1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
|
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head>
<meta http-equiv="Content-Type" content="application/xhtml+xml; charset=UTF-8" />
<meta name="generator" content="AsciiDoc 8.6.9" />
<title></title>
<style type="text/css">
/*
* compact_subsurface.css, a special style sheet for Subsurface,
* modified by Willem Ferguson and derived from:
* compact.css, version 1.3 by Alex Efros <powerman@powerman.name>
* Licence: Public Domain
*
* Usage: asciidoc -a theme=compact_subsurface ...
*/
* { padding: 0; margin: 0; }
img { border: 0; }
/*** Layout ***/
body { margin: 10px 20px; }
#header br { display: none; }
#revnumber { display: block; }
#toc { margin: 1em 0; }
.toclevel2 { margin-left: 1em; }
.toclevel3 { margin-left: 2em; }
#footer { margin-top: 2em; }
#preamble .sectionbody,
h2,
h3,
h4,
h5 { margin: 1em 0 0 0; }
.admonitionblock,
.listingblock,
.sidebarblock,
.exampleblock,
.tableblock,
.literalblock { margin: 1em 0; }
.admonitionblock td.icon { padding-right: 0.5em; }
.admonitionblock td.content { padding-left: 0.5em; }
.listingblock .content { padding: 0.5em; }
.sidebarblock > .content { padding: 0.5em; }
.exampleblock > .content { padding: 0 0.5em; }
.tableblock caption { padding: 0 0 0.5em 0; }
.tableblock thead th,
.tableblock tbody td,
.tableblock tfoot td { padding: 0 0.5em; }
.quoteblock { padding: 0 2.0em; }
.paragraph { margin: 1em 0 0 0; }
.sidebarblock .paragraph:first-child,
.exampleblock .paragraph:first-child,
.admonitionblock .paragraph:first-child { margin: 0; }
.ulist, .olist, .dlist, .hdlist, .qlist { margin: 1em 0; }
li .ulist, li .olist, li .dlist, li .hdlist, li .qlist,
dd .ulist, dd .olist, dd .dlist, dd .hdlist, dd .qlist { margin: 0; }
ul { margin-left: 1.5em; }
ol { margin-left: 2em; }
dd { margin-left: 3em; }
td.hdlist1 { padding-right: 1em; }
/*** Fonts ***/
body { font-family: Verdana, sans-serif; }
#header { font-family: Arial, sans-serif; }
#header h1 { font-family: Arial, sans-serif; }
#footer { font-family: Georgia, serif; }
#email { font-size: 0.85em; }
#revnumber { font-size: 0.75em; }
#toc { font-size: 0.9em; }
#toctitle { font-weight: bold; }
#footer { font-size: 0.8em; }
h2, h3, h4, h5, .title { font-family: Arial, sans-serif; }
h2 { font-size: 1.5em; }
.sectionbody { font-size: 0.85em; }
.sectionbody .sectionbody { font-size: inherit; }
h3 { font-size: 159%; } /* 1.35em */
h4 { font-size: 141%; } /* 1.2em */
h5 { font-size: 118%; } /* 1em */
.title { font-size: 106%; /* 0.9em */
font-weight: bold;
}
tt, .monospaced { font-family: monospace; font-size: 106%; } /* 0.9em */
dt, td.hdlist1, .qlist em { font-family: Times New Roman, serif;
font-size: 118%; /* 1em */
font-style: italic;
}
.tableblock tfoot td { font-weight: bold; }
/*** Colors and Backgrounds ***/
h1 { color: #527bbd; border-bottom: 2px solid silver; }
#footer { border-top: 2px solid silver; }
h2 { color: #527bbd; border-bottom: 2px solid silver; }
h3 { color: #5D7EAE; border-bottom: 2px solid silver; }
h3 { display: inline-block; }
h4,h5 { color: #5D7EAE; }
.admonitionblock td.content { border-left: 2px solid silver; }
.listingblock .content { background: #f4f4f4; border: 1px solid silver; border-left: 5px solid #e0e0e0; }
.sidebarblock > .content { background: #ffffee; border: 1px solid silver; border-left: 5px solid #e0e0e0; }
.exampleblock > .content { border-left: 2px solid silver; }
.quoteblock { border-left: 5px solid #e0e0e0; }
.tableblock table {
border-collapse: collapse;
border-width: 3px;
border-color: #527bbd;
}
.tableblock table[frame=hsides] { border-style: solid none; }
.tableblock table[frame=border] { border-style: solid; }
.tableblock table[frame=void] { border-style: none; }
.tableblock table[frame=vsides] { border-style: none solid; }
.tableblock table[rules=all] tbody tr *,
.tableblock table[rules=rows] tbody tr * {
border-top: 1px solid #527bbd;
}
.tableblock table[rules=all] tr *,
.tableblock table[rules=cols] tr * {
border-left: 1px solid #527bbd;
}
.tableblock table tbody tr:first-child * {
border-top: 1px solid white; /* none don't work here... %-[] */
}
.tableblock table tr *:first-child {
border-left: none;
}
.tableblock table[frame] thead tr *,
.tableblock table[frame] thead tr * {
border-top: 1px solid white;
border-bottom: 2px solid #527bbd;
}
.tableblock table tr td p.table,
.tableblock table tr td p.table * {
border: 0px;
}
tt, .monospaced { color: navy; }
li { color: #a0a0a0; }
li > * { color: black; }
span.aqua { color: aqua; }
span.black { color: black; }
span.blue { color: blue; }
span.fuchsia { color: fuchsia; }
span.gray { color: gray; }
span.green { color: green; }
span.lime { color: lime; }
span.maroon { color: maroon; }
span.navy { color: navy; }
span.olive { color: olive; }
span.purple { color: purple; }
span.red { color: red; }
span.silver { color: silver; }
span.teal { color: teal; }
span.white { color: white; }
span.yellow { color: yellow; }
span.aqua-background { background: aqua; }
span.black-background { background: black; }
span.blue-background { background: blue; }
span.fuchsia-background { background: fuchsia; }
span.gray-background { background: gray; }
span.green-background { background: green; }
span.lime-background { background: lime; }
span.maroon-background { background: maroon; }
span.navy-background { background: navy; }
span.olive-background { background: olive; }
span.purple-background { background: purple; }
span.red-background { background: red; }
span.silver-background { background: silver; }
span.teal-background { background: teal; }
span.white-background { background: white; }
span.yellow-background { background: yellow; }
span.big { font-size: 2em; }
span.small { font-size: 0.6em; }
span.underline { text-decoration: underline; }
span.overline { text-decoration: overline; }
span.line-through { text-decoration: line-through; }
/*** Misc ***/
.admonitionblock td.icon { vertical-align: top; }
.attribution { text-align: right; }
ul { list-style-type: disc; }
ol.arabic { list-style-type: decimal; }
ol.loweralpha { list-style-type: lower-alpha; }
ol.upperalpha { list-style-type: upper-alpha; }
ol.lowerroman { list-style-type: lower-roman; }
ol.upperroman { list-style-type: upper-roman; }
.hdlist td { vertical-align: top; }
</style>
<script type="text/javascript">
/*<+'])');
// Function that scans the DOM tree for header elements (the DOM2
// nodeIterator API would be a better technique but not supported by all
// browsers).
var iterate = function (el) {
for (var i = el.firstChild; i != null; i = i.nextSibling) {
if (i.nodeType == 1 /* Node.ELEMENT_NODE */) {
var mo = re.exec(i.tagName);
if (mo && (i.getAttribute("class") || i.getAttribute("className")) != "float") {
result[result.length] = new TocEntry(i, getText(i), mo[1]-1);
}
iterate(i);
}
}
}
iterate(el);
return result;
}
var toc = document.getElementById("toc");
if (!toc) {
return;
}
// Delete existing TOC entries in case we're reloading the TOC.
var tocEntriesToRemove = [];
var i;
for (i = 0; i < toc.childNodes.length; i++) {
var entry = toc.childNodes[i];
if (entry.nodeName.toLowerCase() == 'div'
&& entry.getAttribute("class")
&& entry.getAttribute("class").match(/^toclevel/))
tocEntriesToRemove.push(entry);
}
for (i = 0; i < tocEntriesToRemove.length; i++) {
toc.removeChild(tocEntriesToRemove[i]);
}
// Rebuild TOC entries.
var entries = tocEntries(document.getElementById("content"), toclevels);
for (var i = 0; i < entries.length; ++i) {
var entry = entries[i];
if (entry.element.id == "")
entry.element.id = "_toc_" + i;
var a = document.createElement("a");
a.href = "#" + entry.element.id;
a.appendChild(document.createTextNode(entry.text));
var div = document.createElement("div");
div.appendChild(a);
div.className = "toclevel" + entry.toclevel;
toc.appendChild(div);
}
if (entries.length == 0)
toc.parentNode.removeChild(toc);
},
/////////////////////////////////////////////////////////////////////
// Footnotes generator
/////////////////////////////////////////////////////////////////////
/* Based on footnote generation code from:
* http://www.brandspankingnew.net/archive/2005/07/format_footnote.html
*/
footnotes: function () {
// Delete existing footnote entries in case we're reloading the footnodes.
var i;
var noteholder = document.getElementById("footnotes");
if (!noteholder) {
return;
}
var entriesToRemove = [];
for (i = 0; i < noteholder.childNodes.length; i++) {
var entry = noteholder.childNodes[i];
if (entry.nodeName.toLowerCase() == 'div' && entry.getAttribute("class") == "footnote")
entriesToRemove.push(entry);
}
for (i = 0; i < entriesToRemove.length; i++) {
noteholder.removeChild(entriesToRemove[i]);
}
// Rebuild footnote entries.
var cont = document.getElementById("content");
var spans = cont.getElementsByTagName("span");
var refs = {};
var n = 0;
for (i=0; i<spans.length; i++) {
if (spans[i].className == "footnote") {
n++;
var note = spans[i].getAttribute("data-note");
if (!note) {
// Use [\s\S] in place of . so multi-line matches work.
// Because JavaScript has no s (dotall) regex flag.
note = spans[i].innerHTML.match(/\s*\[([\s\S]*)]\s*/)[1];
spans[i].innerHTML =
"[<a id='_footnoteref_" + n + "' href='#_footnote_" + n +
"' title='View footnote' class='footnote'>" + n + "</a>]";
spans[i].setAttribute("data-note", note);
}
noteholder.innerHTML +=
"<div class='footnote' id='_footnote_" + n + "'>" +
"<a href='#_footnoteref_" + n + "' title='Return to text'>" +
n + "</a>. " + note + "</div>";
var id =spans[i].getAttribute("id");
if (id != null) refs["#"+id] = n;
}
}
if (n == 0)
noteholder.parentNode.removeChild(noteholder);
else {
// Process footnoterefs.
for (i=0; i<spans.length; i++) {
if (spans[i].className == "footnoteref") {
var href = spans[i].getElementsByTagName("a")[0].getAttribute("href");
href = href.match(/#.*/)[0]; // Because IE return full URL.
n = refs[href];
spans[i].innerHTML =
"[<a href='#_footnote_" + n +
"' title='View footnote' class='footnote'>" + n + "</a>]";
}
}
}
},
install: function(toclevels) {
var timerId;
function reinstall() {
asciidoc.footnotes();
if (toclevels) {
asciidoc.toc(toclevels);
}
}
function reinstallAndRemoveTimer() {
clearInterval(timerId);
reinstall();
}
timerId = setInterval(reinstall, 500);
if (document.addEventListener)
document.addEventListener("DOMContentLoaded", reinstallAndRemoveTimer, false);
else
window.onload = reinstallAndRemoveTimer;
}
}
asciidoc.install(3);
/*]]>*/
</script>
</head>
<body class="article">
<div id="header">
</div>
<div id="content">
<div class="imageblock" style="text-align:center;">
<div class="content">
<img src="mobile-images/banner.jpg" alt="Banner" />
</div>
</div>
<div class="paragraph"><p><span class="big">MANUEL UTILISATEUR de Subsurface-mobile</span></p></div>
<div class="paragraph"><p><strong>Auteurs du manuel</strong> : Willem Ferguson, Dirk Hohndel</p></div>
<div id="toc">
<div id="toctitle">Table of Contents</div>
<noscript><p><b>JavaScript must be enabled in your browser to display the table of contents.</b></p></noscript>
</div>
<div class="paragraph"><p><span class="blue"><em>Version 2, juillet 2017</em></span></p></div>
<div class="paragraph"><p>Welcome as a user of <em>Subsurface</em>, advanced dive logging software with
extensive infrastructure to describe, organize, interpret and print scuba
and free dives. <em>Subsurface</em> offers many advantages over other similar
software solutions, including compatibility with Windows, Mac-OS/X, Linux
(many distributions), Android and iOS. In addition, <em>Subsurface</em> is
open-source software that allows downloading dive information from most dive
computers.</p></div>
<div class="sect1">
<h2 id="_présentation_de_subsurface_mobile">1. Présentation de Subsurface-mobile</h2>
<div class="sectionbody">
<div class="paragraph"><p><em>Subsurface-mobile</em> est une extension de <em>Subsurface</em> qui fonctionne sur les
smartphones Android et iOS et sur les tablettes. C’est un outil pour
visualiser et partager des informations de plongées sur des sites de
plongées où un ordinateur n’est pas utile. <em>Subsurface-mobile</em> permet
également de collecter des positions GPS où sont effectuées les
plongées. (Subsurface-mobile pour iOS ne supporte pas toutes les fonctions
pour le moment).</p></div>
<div class="paragraph"><p><em>Subsurface-mobile</em> allows you to enter and save dive information using a
mobile device. Users of <em>Subsurface-mobile</em> typically use the mobile app as
an extension to the laptop/desktop version of <em>Subsurface</em> that allows the
storage of dive logs on the Internet and sharing them between the mobile and
the desktop versions. But <em>Subsurface-mobile</em> can also be used independently
of <em>Subsurface</em> and does not require the use of cloud storage. While the
desktop version of <em>Subsurface</em> shows much more detailed information for
each dive, the mobile version allows a more accessible dive log on a dive
trip, useful for proving dive experience to dive shops or to review previous
dives.</p></div>
<div class="paragraph"><p><em>Subsurface-mobile</em> allows you to:</p></div>
<div class="ulist"><ul>
<li>
<p>
Download existing dive log information from the Internet.
</p>
</li>
<li>
<p>
View this information on a mobile device.
</p>
</li>
<li>
<p>
Edit many of the dive log data fields, e.g. divemaster, buddy, equipment or
notes about a dive.
</p>
</li>
<li>
<p>
Manually create and add new dive records to your dive log.
</p>
</li>
<li>
<p>
Download dive data directly from many dive computers.
</p>
</li>
<li>
<p>
Store the updated dive log in the <em>Subsurface</em> cloud storage.
</p>
</li>
<li>
<p>
Record, store and apply GPS positions of dives (Android only).
</p>
</li>
<li>
<p>
View the localities of recorded GPS positions and of dives on a map.
</p>
</li>
</ul></div>
<div class="paragraph"><p>These items are discussed in greater detail in the following text.
<em>Subsurface-mobile</em> does not yet support download of dive data from all the
dive computers that the desktop/laptop version can: that still needs to be
done using <em>Subsurface</em> on a desktop or laptop computer. Only a subset of
dive computers that use a FTDI USB interface or a Bluetooth/BTLE interface
are accessible by <em>Subsurface-mobile</em>.</p></div>
</div>
</div>
<div class="sect1">
<h2 id="_installing_em_subsurface_mobile_em_on_your_mobile_device">2. Installing <em>Subsurface-mobile</em> on your mobile device</h2>
<div class="sectionbody">
<div class="paragraph"><p>Find <em>Subsurface-mobile</em> in the <em>Google Play Store</em> or the <em>iTunes Store</em>
and install it.</p></div>
</div>
</div>
<div class="sect1">
<h2 id="_using_em_subsurface_mobile_em_for_the_first_time">3. Using <em>Subsurface-mobile</em> for the first time</h2>
<div class="sectionbody">
<div class="paragraph"><p>Upon starting <em>Subsurface-mobile</em> for the first time, a Subsurface splash
screen is shown while the program loads. On some devices this may take
several seconds. After loading, the <em>Cloud Credentials screen</em> appears (see
image below on left).</p></div>
<div class="paragraph"><p>Select whether <em>Subsurface-mobile</em> should access the Internet for dive log
information as follows:</p></div>
<div class="sect2">
<h3 id="_when_not_using_cloud_storage">3.1. When NOT Using Cloud Storage</h3>
<div class="paragraph"><p>Tap the striked-out cloud icon. The app will not access the <em>Subsurface</em>
cloud storage server to obtain dive log information. This means that dive
log information is stored on the mobile device only.</p></div>
</div>
<div class="sect2">
<h3 id="_using_cloud_storage">3.2. Using Cloud Storage</h3>
<div class="paragraph"><p>In order to use the <em>Subsurface</em> cloud storage, an account on the cloud
server is required. If you have already set up an account from the
<em>Subsurface</em> desktop application, enter the credentials here.</p></div>
<div class="paragraph"><p>You can also create a new cloud storage account from your mobile device.</p></div>
<div class="sect3">
<h4 id="_using_the_desktop_version_of_em_subsurface_em">3.2.1. Using the desktop version of <em>Subsurface</em>:</h4>
<div class="paragraph"><p>Open the desktop version of <em>Subsurface</em> and
click <em>File → Preferences → Network</em>, explained in detail in the
<a href="https://subsurface-divelog.org/documentation/subsurface-4-user-manual/#_create_a_cloud_storage_account">user
manual for the <em>Subsurface</em> desktop version</a>. Once the account has
been created and verified using the desktop version,
<em>Subsurface</em> desktop alows you to download dive information from dive computers and store this
on the cloud which can, in turn, be downloaded to <em>Subsurface-mobile</em>. <em>Subsurface-mobile</em>
attempts to download the existing dive log from the <em>Subsurface</em> cloud
server. Appropriate messages are shown onscreen. Finally a list of dives is shown.</p></div>
<div class="paragraph"><p>Once the dive list has been downloaded from the Internet,
<em>Subsurface-mobile</em> keeps a local copy on the mobile device. This means that
even if there is no Internet connection at a dive site, you can still access
the local copy and view and manipulate dive information. If there is
Internet connectivity, <em>Subsurface-mobile</em> accesses the cloud-based dive log
to verify that the local copy is still the same as the Internet-stored
copy. If not, the local copy and the copy on the server are synchronised.</p></div>
<div class="imageblock" style="text-align:center;">
<div class="content">
<img src="mobile-images/Credentials.jpg" alt="FIGURE: Mobile landing screen" />
</div>
</div>
</div>
<div class="sect3">
<h4 id="_using_em_subsurface_mobile_em">3.2.2. Using <em>Subsurface-mobile</em>:</h4>
<div class="paragraph"><p>Enter an e-mail address and a password in the fields indicated on the
screen. The e-mail should be in lower case and the password should contain
a combination of letters from the alphabet (upper and lower case) and/or
numbers. When entering a password, it is possible to check a checkbox that
enables the text of the password to be shown (image on left, above). At this
stage, the red message "Cannot connect to cloud storage" appears on the
screen. This is normal because a valid PIN has not yet been provided (image
on left, above).</p></div>
<div class="paragraph"><p>Tap the Disk (Save) icon at the bottom of the screen. A PIN is sent to the
e-mail address provided.</p></div>
<div class="paragraph"><p>Enter the PIN into the field indicated and tap the <em>Save</em> icon again. The
user information is stored on the cloud server and access to the cloud is
enabled.</p></div>
<div class="paragraph"><p>The dive list is initially empty. Start entering dives in the dive log or
download dive information from either a <em>Subsurface</em> cloud storage account
or from a dive computer.</p></div>
</div>
</div>
</div>
</div>
<div class="sect1">
<h2 id="_menu_structure_and_user_interface">4. Menu Structure and User Interface</h2>
<div class="sectionbody">
<div class="paragraph"><p>At the bottom of many Subsurface-mobile screens is a round button that
provides for several actions and which allows the selection of the main
affirmative action (see image above and image below). On Android devices,
use the Android Back button for "cancel", "discard" or "back" actions. For
example, when editing dive information, tapping the action button saves the
changes while the Android back button can be used to cancel the edit without
saving changes.</p></div>
<div class="paragraph"><p>On iOS devices, on screens where a "back" action is enabled, a back arrow is
shown in the top left corner of the screen.</p></div>
<div class="imageblock" style="text-align:center;">
<div class="content">
<img src="mobile-images/actionbutton.jpg" alt="FIGURE: Action Button" />
</div>
</div>
<div class="paragraph"><p>In order to have a consistent experience between iOS and Android,
<em>Subsurface-mobile</em> on Android does not use the traditional "hamburger" menu
button in the top left or right corner of the screen to open menus.
Instead, <em>Subsurface-mobile</em> uses a different user interaction philosophy
based on the Kirigami framework developed by the Plasma developers. There
are three ways to open the main menu:</p></div>
<div class="ulist"><ul>
<li>
<p>
Tap the "hamburger" symbol in the lower left corner of the screen (easy to
reach for hand held devices)
</p>
</li>
<li>
<p>
Swipe towards the right across the left edge of the screen
</p>
</li>
<li>
<p>
Drag the action button visible on most screens to the right
</p>
</li>
</ul></div>
<div class="imageblock" style="text-align:center;">
<div class="content">
<img src="mobile-images/MainMenu2.jpg" alt="FIGURE: Dive management subpanel" />
</div>
</div>
<div class="paragraph"><p>The images above indicate some of the important features of the menu
system. On the left is the main menu, activated as described above. On the
right, above, is a representation of the menu items of all the submenus
accessible from the main menu: the main menu items are shown on the left
while the submenu contents are shown on a blue background on the right.</p></div>
<div class="paragraph"><p>All screenshots in this user manual are currently from the Android
version. As indicated earlier, the iOS version currently doesn’t support
<em>GPS</em> features.</p></div>
</div>
</div>
<div class="sect1">
<h2 id="_viewing_the_dive_list">5. Viewing the Dive List</h2>
<div class="sectionbody">
<div class="paragraph"><p>Most of the actions of <em>Subsurface-mobile</em> center around the dives on the
dive list. While the dive list is loading from the cloud, a message appears
at the bottom of the screen, indicating that the cloud is being
accessed. Once the list is loaded you can scroll up and down. Tapping a
dive on the list brings up a display of <em>Details View</em> for that dive (see
image on right below). This includes the dive profile as well as additional
information and notes.</p></div>
<div class="imageblock" style="text-align:center;">
<div class="content">
<img src="mobile-images/DiveList.jpg" alt="FIGURE: Dive list screen" />
</div>
</div>
<div class="paragraph"><p>You can view other dives by swiping the <em>Details view</em> to the right (for the
previous dive) or to the left (following dive). Using the Action Bar, it is
also possible to delete the dive (tap the dustbin on the Action Bar) or to
view the dive location on a map viewer (Google Maps on Android, the Google
Maps web site on iOS; tap the GPS icon on the Action Bar.).</p></div>
</div>
</div>
<div class="sect1">
<h2 id="S_Edit_Dive">6. Editing dive details</h2>
<div class="sectionbody">
<div class="paragraph"><p>At the bottom of the dive details screen the <em>Action Button</em> contains a
pencil (image on right, above). Tapping the pencil button brings up a panel
with edit boxes that allows you to change the existing dive information,
e.g. adding text to the dive notes or changing the names or values of some
of the information (see image below). It may be necessary to scroll the
window to access all the information. At the bottom of the edit screen is a
<em>Save</em> action button. Tap this to save the new information. Having saved the
data, the dive list screen is updated and shown. To cancel any edits, tap
the Android Back Button or swipe the edit screen up (fling it away).</p></div>
<div class="imageblock" style="text-align:center;">
<div class="content">
<img src="mobile-images/EditDive.jpg" alt="FIGURE: Dive edit screen" />
</div>
</div>
</div>
</div>
<div class="sect1">
<h2 id="S_Add_Dive">7. Adding a new dive to the dive list</h2>
<div class="sectionbody">
<div class="paragraph"><p>You can manually add a dive to the existing dive list. On the dive list tap
the "plus" sign in the <em>Action Button</em>, or use the main menu and tap <em>Manage
dives → Add dive manually</em>. This opens a screen that is identical to the
editing screen discussed above. When a dive is added manually, you cannot
directly add a dive profile from a dive computer. However, if you do not use
a dive computer, the duration, depth and several other bits of information
about the new dive can be entered. The <em>Action button</em> at the bottom of the
screen contains a disk symbol. Tap this to save the new dive. To cancel any
edits, tap the Android Back Button. The left-hand image below shows a
screenshot of a dive being created and the right-hand image shows the same
dive in <em>Details View</em>.</p></div>
<div class="imageblock" style="text-align:center;">
<div class="content">
<img src="mobile-images/ManuallyEnterDive.jpg" alt="FIGURE: Manual dive entry screen" />
</div>
</div>
</div>
</div>
<div class="sect1">
<h2 id="_deleting_a_dive">8. Deleting a dive</h2>
<div class="sectionbody">
<div class="paragraph"><p>The <em>Details View</em> of a dive has an Action Bar, including a dustbin. If this
is tapped, the dive shown in the <em>Details View</em> is deleted. You have a brief
opportunity to undo the delete by tapping the grey <em>Undo</em> button in the
message that appears at the bottom of the screen (see image below).</p></div>
<div class="imageblock" style="text-align:center;">
<div class="content">
<img src="mobile-images/Delete_undo.jpg" alt="FIGURE: Undo delete dive" />
</div>
</div>
<div class="paragraph"><p>You can also delete a dive from the dive list by long-pressing a specific
dive until a red dustbin appears on the right-hand side (see image
below). Tap the dustbin. The dive is deleted without asking any confirmation
because <em>Subsurface-mobile</em> assumes that the combination of a long tap on
the dive with another tap on the red dustbin is an unambiguous instruction
to delete the dive.</p></div>
<div class="imageblock" style="text-align:center;">
<div class="content">
<img src="mobile-images/RedDustbin.jpg" alt="FIGURE: delete dive from list" />
</div>
</div>
</div>
</div>
<div class="sect1">
<h2 id="_download_dives_from_a_dive_computer">9. Download dives from a dive computer</h2>
<div class="sectionbody">
<div class="paragraph"><p>Download of dives is possible from dive computers with a FTDI USB interface,
or with a Bluetooth interface.</p></div>
<div class="paragraph"><p>First, establish a link between the dive computer and the mobile device.</p></div>
<div class="paragraph"><p>For USB dive computers, USB cables "normally" used for uploading dives to a
desktop/laptop computer do NOT work: these cables often have a full-sized
male USB plug on one end which plugs into the USB port of a desktop/laptop
computer. For downloads to a mobile device one needs a USB OTG (USB
On-The-Go) cable. In most cases it is required to plug the USB cable
"normally" used with the dive computer into a USB OTG cable which, in turn,
plugs into the mini-USB receptacle of the mobile device. The OTG cable often
has a full-size female receptacle at one end which accommodates the
full-sized male plug of the USB cable "normally" used (see image
below). This means that two cables are used to connect the dive computer to
the mobile device.</p></div>
<div class="imageblock" style="text-align:center;">
<div class="content">
<img src="mobile-images/USB-OTG.jpg" alt="FIGURE: USB-OTG cable" />
</div>
</div>
<div class="paragraph"><p>For Bluetooth-equipped dive computers, establish a Bluetooth connection
between the dive computer and the mobile device. Use the tools on the mobile
device to achieve this. For of Android mobile devices, the Settings →
Bluetooth tool is probably appropriate. Ensure pairing of the dive computer
and mobile device. <em>Subsurface-mobile</em> performs communication using both
Bluetooth and Bluetooth-low-energy (BTLE). The appropriate choice of
Bluetooth communication is made by the software and the user need not be
concerned with this.</p></div>
<div class="paragraph"><p>With propper communication between dive computer and <em>Subsurface-mobile</em>
having been set up, dive download is simple. From the main menu, tap
<em>Manage dives → Download from DC</em>. A screen is shown requiring that the
user specify the names of the vendor and model of the dive computer. For
instance, when using a Shearwater Petrel 2 dive computer, the vendor is
<em>Shearwater</em> and the Dive computer name is <em>Petrel 2</em>. From the two dropdown
lists at the top of the screen, select the correct vendor and dive computer
names (see image on the left, below). If using a dive computer using a
Bluetooth connection, then tap the check box labelled <em>Bluetooth download</em>.</p></div>
<div class="paragraph"><p>Now tap the button labled <em>DOWNLOAD</em>. The downloaded dives appear in the
bottom part of the screen, the most recent dive at the top (see image on
right, below). Be patient because the download can sometimes take a few
mimnutes. Each dive has a check-box on the left hand side, used for
selecting which dives need to be added to the <em>Subsurface-mobile</em> dive list:
dives that are not checked are ignored. With the appropriate downloaded
dives having been checked, tap the button at the bottom left labled
<em>ACCEPT</em>. All the selected dives appear on the <em>Subsurface-mobile</em> dive
list. The downloaded dive information can now be edited as described in the
section above <a href="#S_Edit_Dive">Edit a dive</a>.</p></div>
<div class="imageblock" style="text-align:center;">
<div class="content">
<img src="mobile-images/DC-Download.jpg" alt="FIGURE: DC download screen" />
</div>
</div>
</div>
</div>
<div class="sect1">
<h2 id="_viewing_the_dive_location_on_google_maps">10. Viewing the dive location on Google Maps</h2>
<div class="sectionbody">
<div class="paragraph"><p>The site of a specific dive can be viewed in two ways using the <em>Details
View</em>. The Action Bar at the bottom has a GPS pin on the left hand
side. Tap that pin and the dive site is shown in Google Maps. Close Google
Maps by using the Android <em>Back</em> button.</p></div>
<div class="paragraph"><p>Alternatively, the <em>Details View</em> has a button at the top right hand marked
<em>Map it</em>. Tap this button to open Google Maps showing the dive site.</p></div>
<div class="imageblock" style="text-align:center;">
<div class="content">
<img src="mobile-images/Map.jpg" alt="FIGURE: Map of dive site" />
</div>
</div>
</div>
</div>
<div class="sect1">
<h2 id="_dive_log_management">11. Dive log management</h2>
<div class="sectionbody">
<div class="paragraph"><p>A central part of <em>Subsurface-mobile</em> is the ability to store the dive log
using the <em>Subsurface</em> cloud storage. This provides security against loss
or damage to the dive information contained in a local copy of the dive log
and allows the desktop version of <em>Subsurface</em> to access changes made using
the mobile device. This ability is accessed through the main menu (by
dragging the Action Button to the right, or alternatively tapping the
"Hamburger" icon at the bottom left of the screen). Tap the option <em>Manage
dives</em>, enabling a number of options:</p></div>
<div class="sect2">
<h3 id="_add_new_dive_manually">11.1. Add new dive manually</h3>
<div class="paragraph"><p>This is described above under the section dealing with
<a href="#S_Add_Dive">Adding a new dive to the dive list</a>.</p></div>
</div>
<div class="sect2">
<h3 id="_sync_the_dive_log_with_the_em_subsurface_em_cloud_storage">11.2. Sync the dive log with the <em>Subsurface</em> cloud storage</h3>
<div class="paragraph"><p>Upload the dives contained on the mobile device to the <em>Subsurface</em> cloud
storage by tapping the option <em>Manual sync with cloud</em>. This synchronizes
the local changes to the dive log with the cloud storage. It also downloads
changes made to the dive log using another device or computer and stored in
cloud storage.</p></div>
</div>
<div class="sect2">
<h3 id="_working_offline_or_online">11.3. Working offline or online</h3>
<div class="paragraph"><p>By default <em>Subsurface-mobile</em> runs offline and only syncs the dive list
with cloud storage when explicily told to do so (see above). You can choose
to always sync with the cloud servers after every modification of the dive
list. This is not recommended unless you are in an area with fast and
reliable internet connection, as otherwise <em>Subsurface-mobile</em> might appear
to hang between operations as it tries to connect to the cloud server.</p></div>
</div>
<div class="sect2">
<h3 id="_changing_the_login_credentials_on_the_em_subsurface_em_cloud">11.4. Changing the login credentials on the <em>Subsurface</em> cloud</h3>
<div class="paragraph"><p>The login credentials (for example to work with multiple accounts) can be
changed by opening the main menu and by tapping <em>Settings → Cloud
credentials</em>. This opens the screen for specifying new credentials.</p></div>
</div>
<div class="sect2">
<h3 id="_changing_the_colour_scheme_of_em_subsurface_mobile_em">11.5. Changing the colour scheme of <em>Subsurface-mobile</em></h3>
<div class="paragraph"><p><em>Subsurface-mobile</em> has three colour schemes to please users with different
tastes. This user manual shows the default colour scheme, comprising blue
colours. Change to a pink or a dark colour scheme by opening the main menu
and tap Settings → Preferences. This opens the Preferences screen that
includes the three colour schemes (see image below).</p></div>
<div class="imageblock" style="text-align:center;">
<div class="content">
<img src="mobile-images/ColourSchemes.jpg" alt="FIGURE: Colour scheme setup screen" />
</div>
</div>
</div>
</div>
</div>
<div class="sect1">
<h2 id="_recording_dive_locations_using_gps_android_only">12. Recording dive locations using GPS (Android only).</h2>
<div class="sectionbody">
<div class="paragraph"><p>The fact that most smartphones have GPS facilities allows
<em>Subsurface-mobile</em> on Android to record the locations of dives. You can
take the smartphone on the dive boat during a dive and locations will be
automatically recorded at regular intervals. These locations can then be
applied to dives in the dive list. Here is how it’s done:</p></div>
<div class="sect2">
<h3 id="_setting_up_the_gps">12.1. Setting up the GPS</h3>
<div class="paragraph"><p>Open the main menu and tap <em>GPS → Preferences</em>. Now specify the way in
which GPS data need to be automatically collected (image above). Data are
collected at regular intervals, e.g. every 5 minutes, or at regular
distances, e.g. after the boat has moved more than 200m, or a combination of
both of these approaches. Provide the appropriate information and tap the
<em>Save</em> action button. The program is now ready to collect GPS positions.</p></div>
</div>
<div class="sect2">
<h3 id="_collecting_gps_positions">12.2. Collecting GPS positions</h3>
<div class="imageblock" style="text-align:center;">
<div class="content">
<img src="mobile-images/Mainmenu.jpg" alt="FIGURE: Main menu" />
</div>
</div>
<div class="paragraph"><p>Ensure that the GPS on the Android device has been activated. At the bottom
of the GPS submenu is a check box <em>Run location service</em> (image above).
Check this box and <em>Subsurface-mobile</em> starts to collect GPS locations
automatically, following the preferences specified as described above. After
return from the dive trip you can deactivate the collection of GPS data by
de-activating the same check box at the bottom of the main menu.</p></div>
</div>
<div class="sect2">
<h3 id="_storing_the_gps_data_on_the_em_subsurface_em_cloud">12.3. Storing the GPS data on the <em>Subsurface</em> cloud</h3>
<div class="paragraph"><p>Activate the main menu and select the <em>GPS</em> option that brings up the
submenu of GPS-related actions. Tap <em>Upload GPS data</em> that saves the GPS
data on the <em>Subsurface</em> cloud server. These GPS data are saved <strong>separately</strong>
from the other dive log data. All collected GPS data are kept on the Android
device, independent of whether they have been uploaded or not.</p></div>
</div>
<div class="sect2">
<h3 id="_downloading_gps_data_from_the_em_subsurface_em_cloud">12.4. Downloading GPS data from the <em>Subsurface</em> cloud</h3>
<div class="paragraph"><p>Download the GPS data that have been saved on the cloud (possibly by a
different device) by selecting <em>Download GPS Data</em> from the GPS subpanel.</p></div>
</div>
<div class="sect2">
<h3 id="_viewing_gps_data">12.5. Viewing GPS data</h3>
<div class="paragraph"><p>From the GPS submenu select <em>Show GPS fixes</em>. This brings up a list of GPS
positions obtained using the location service (image on left, below). Two
actions are possible for each of the locations, enabled if you tap the
handle (the three horisontal stripes on the right, see image on left, below)
and then drags the specific item to the left (image on right, below). This
exposes two options. Tapping the dustbin deletes this particular GPS
location. Tapping the teardrop-shaped icon (actually a Google Maps pin)
opens up Google Maps with a pin indicating the exact map position of the GPS
record being viewed. The two above options can be hidden by drawing the GPS
record to the right, again using the handle.</p></div>
<div class="imageblock" style="text-align:center;">
<div class="content">
<img src="mobile-images/gpsmanagement.jpg" alt="FIGURE: GPS management" />
</div>
</div>
</div>
<div class="sect2">
<h3 id="_applying_gps_data_to_dives_in_the_dive_log">12.6. Applying GPS data to dives in the dive log</h3>
<div class="paragraph"><p>Assuming that all the dives have been entered into the dive log or have been
downloaded from the <em>Subsurface</em> cloud, you can apply the GPS positions to
these dives. GPS positions can therefore only be applied to dives in the
dive list. From the GPS subpanel, tap <em>GPS-tag dives</em>. The dive list
contains the start and end times of each dive. Now, <em>Subsurface-mobile</em>
applies the first GPS position that falls within the dive period of each
dive. This results in a GPS position for each dive that is saved as part of
the dive log.</p></div>
</div>
</div>
</div>
</div>
<div id="footnotes"><hr /></div>
<div id="footer">
<div id="footer-text">
Last updated
2017-10-11 10:34:38 CEST
</div>
</div>
</body>
</html>
|
