Android App

[Dirk Hohndel]

I would like to update the app. It would be nice if a few people could try the 
new Subsurface-mobile that's available in the beta test channel... Just as a 
check to make sure I didn't break anything obvious

Thanks

/D

⁣--
>From my phone​___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Android app

[Dirk Hohndel]

I pushed the latest version (with quite a few Kirigami updates) to both 
downloads/test and Google Play Beta.
I'll need to redo all the screen shots. Again. But I really think the look is 
coming together.

Jocke and Jan - are you still working on the UI? There were still a few things 
that needed updates, especially the entering of credentials...
It would be nice to get Subsurface-mobile on Android to a stage where we feel 
good to do a release.

Thanks for your help

/D
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Android APP

[Leo Ekelmans via subsurface]

Dear Subsurface developpers,

I am a happy user of the subsurface programs on Android, ipad and mac book.
Unfortunately since the latest Android update of May 27th the app is
crashing on my Samsung A52. Not sure if this has been reported sofar

Regards,
Leo
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

subsurface android app

[Joachim Herrmann]

Dear subsurface developpers, 
I am a user of your Desktop application. Today I had the idea to use your 
cloud-service to access my dives on my android phone. 

SO I got myself an account and confirmed it through email. 
After installing the app on my phone  I entered my User Id, checked that the 
API URL is correct and did everything I could think of with the same result : 
„no dives“. 

Going through my browser on my tablet using the same ID showed me my dives on 
your Server. Subsurface also shows my dives when I use „file ->Open Cloud 
storage“ 

What do I do wrong in the android app ? 

Kind regards 

Joachim Herrmann
Northeim, Germany

Gesendet von Mail für Windows 10

___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Android app -755

[Dirk Hohndel]

More poking in the dark by a blind hacker. But it seems I'm slowly getting
the hang of a few things. Tomaz / Sebastian - I'd appreciate if you could
look over my last dozen commits. I've done some more advanced Qt hacking
(at least more advanced than my usual dabbling) in commit af9f07626a01 and
used that in the following commits to be able to actually poke at the data
in the model (which made things so much simpler for me). This still isn't
perfect, I can still get to a point where I'm not highlighting the correct
dive, but it seems much more reliable.

I also dealt with more weird layout issues and appear to have figured out
a clean way to know how wide a column is supposed to be. Sebastian, I'd
appreciate if you could take a look at that in commit ba4bb5670192. This
does recreate code that's in PageRow.qml, but I didn't manage to reliably
extract the columnWidth variable from there whereas this way seems to be
easy and accessible from anywhere in the code.

Anyway, I'd appreciate a fresh round of testing. This should close a
number of outstanding bugs.

And I'm sure I have successfully added a few new ones in return :-)

/D
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Android app -923

[Dirk Hohndel]

This is back to using Qt 5.6.0.
In order to avoid the crashes we've been seeing with that I now switched
the grid layout on the dive details page to be fixed column width (so
we're setting both the preferred and the maximum width to the same value).

The notification for cloud access seems to work in all the scenarios that
I could think of testing.

The list of known outstanding bugs is getting really small.

Sebas, now that we are on Qt 5.6... do you remember what you and I tested
a couple of months ago with getting the correct keyboard geometry from Qt?
I know that worked with 5.6... so maybe you could create a Kirigami patch
to use that data so the users don't need to close the keyboard to access
the bottom part of a page?

Other than that... localization, but I'm OK with having the first release
just in English, to be honest. What else is broken?

I'll give it a day (since the Europeans most likely are asleep by now) and
then maybe make another beta tomorrow. And then maybe we can work our way
towards a first release next week?

/D
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Android App

[Willem Ferguson]

>From phone. Where does one find the beta test channel? Kind regards, willem

On 12 Mar 2017 04:32, "Dirk Hohndel"  wrote:

I would like to update the app. It would be nice if a few people could try
the new Subsurface-mobile that's available in the beta test channel... Just
as a check to make sure I didn't break anything obvious

Thanks

/D

-- 
>From my phone

___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Android App

[Miika Turkia]

I believe it is this one from another thread 3 hours ago:

https://play.google.com/apps/testing/org.subsurfacedivelog.mobile

miika

On Sun, Mar 12, 2017 at 7:28 AM, Willem Ferguson
 wrote:
> From phone. Where does one find the beta test channel? Kind regards, willem
>
> On 12 Mar 2017 04:32, "Dirk Hohndel"  wrote:
>
> I would like to update the app. It would be nice if a few people could try
> the new Subsurface-mobile that's available in the beta test channel... Just
> as a check to make sure I didn't break anything obvious
>
> Thanks
>
> /D
>
> --
> From my phone
>
> ___
> subsurface mailing list
> subsurface@subsurface-divelog.org
> http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
>
>
>
> ___
> subsurface mailing list
> subsurface@subsurface-divelog.org
> http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
>
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Android App

[Anton Lundin]

On 11 March, 2017 - Dirk Hohndel wrote:

> I would like to update the app. It would be nice if a few people could try 
> the new Subsurface-mobile that's available in the beta test channel... Just 
> as a check to make sure I didn't break anything obvious
> 

LGTM


//Anton


-- 
Anton Lundin+46702-161604
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Android App

[Jérémie Guichard]

Made a fast walk through, did not find anything significant...

2017-03-12 14:19 GMT+07:00 Anton Lundin :

> On 11 March, 2017 - Dirk Hohndel wrote:
>
> > I would like to update the app. It would be nice if a few people could
> try the new Subsurface-mobile that's available in the beta test channel...
> Just as a check to make sure I didn't break anything obvious
> >
>
> LGTM
>
>
> //Anton
>
>
> --
> Anton Lundin+46702-161604
> ___
> subsurface mailing list
> subsurface@subsurface-divelog.org
> http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
>
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Android App

[Jan Van Winkel]

Works as before and thanks for the great job

But I spotted two minor issues, the first one I noticed yesterday so it was
also present in the previous version.
The second one I encountered today with the new version when I was trying
to reproduce the first one.

Issue 1:  Select latests dive (X), swipe to previous dive (X-1), rotate
phone, rotate back -> next dive is shown (X-2)
Note that the dive name at the top (after Dive List) is still the name of
 dive X-1 and the swipe direction (bak or forward) has no impact on the
miss behavior .
Further if the rotation is repeated the correct dive is shown (X-1 instead
of X-2) and the issue is not reproducible anymore until a swipe is
performed.

Issue 2: Incorrect dive opened after selection (X = last dive)
Select dive X-1, dive X-2 is opened instead.
Problem only impact dives shown immediately after starting the app, dives
selected after scrolling are not impacted.
Selecting dive X-1 a second time opens X-1.

Phone: Moto G4 Play (xt1602)
Android version: 6.0.1 (Marshmallow)
App version: 1.2.0 (4.6.3.78)

Shall I create issues for them on github or keep them here on the list?

Regards,
Jan

On Sun, Mar 12, 2017 at 3:32 AM Dirk Hohndel  wrote:

> I would like to update the app. It would be nice if a few people could try
> the new Subsurface-mobile that's available in the beta test channel... Just
> as a check to make sure I didn't break anything obvious
>
> Thanks
>
> /D
>
> --
> From my phone
> ___
> subsurface mailing list
> subsurface@subsurface-divelog.org
> http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
>
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Android App

[Dirk Hohndel]

Please create two issues. That way we at least track this.

⁣--
>From my phone​


 Original Message 
From: Jan Van Winkel 
Sent: Sun Mar 12 04:56:48 PDT 2017
To: Dirk Hohndel , Subsurface Mailing List 

Subject: Re: Android App

Works as before and thanks for the great job

But I spotted two minor issues, the first one I noticed yesterday so it was
also present in the previous version.
The second one I encountered today with the new version when I was trying
to reproduce the first one.

Issue 1:  Select latests dive (X), swipe to previous dive (X-1), rotate
phone, rotate back -> next dive is shown (X-2)
Note that the dive name at the top (after Dive List) is still the name of
 dive X-1 and the swipe direction (bak or forward) has no impact on the
miss behavior .
Further if the rotation is repeated the correct dive is shown (X-1 instead
of X-2) and the issue is not reproducible anymore until a swipe is
performed.

Issue 2: Incorrect dive opened after selection (X = last dive)
Select dive X-1, dive X-2 is opened instead.
Problem only impact dives shown immediately after starting the app, dives
selected after scrolling are not impacted.
Selecting dive X-1 a second time opens X-1.

Phone: Moto G4 Play (xt1602)
Android version: 6.0.1 (Marshmallow)
App version: 1.2.0 (4.6.3.78)

Shall I create issues for them on github or keep them here on the list?

Regards,
Jan

On Sun, Mar 12, 2017 at 3:32 AM Dirk Hohndel  wrote:

> I would like to update the app. It would be nice if a few people could try
> the new Subsurface-mobile that's available in the beta test channel... Just
> as a check to make sure I didn't break anything obvious
>
> Thanks
>
> /D
>
> --
> From my phone
> ___
> subsurface mailing list
> subsurface@subsurface-divelog.org
> http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
>
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Android App

[Dirk Hohndel]

Thanks for the quick reality check, folks. I just moved the app from Beta
to Production - I forgot to do that when we did the last update (that
fixed the multi-buddy edit), so the production app was from last August.

Oops.

Need to be better about keeping the mobile apps updated. Which reminds me,
I also need to do a new iOS release. Grmbl

/D

On Sun, Mar 12, 2017 at 02:53:57PM +0700, Jérémie Guichard wrote:
> Made a fast walk through, did not find anything significant...
> 
> 2017-03-12 14:19 GMT+07:00 Anton Lundin :
> 
> > On 11 March, 2017 - Dirk Hohndel wrote:
> >
> > > I would like to update the app. It would be nice if a few people could
> > try the new Subsurface-mobile that's available in the beta test channel...
> > Just as a check to make sure I didn't break anything obvious
> > >
> >
> > LGTM
> >
> >
> > //Anton
> >
> >
> > --
> > Anton Lundin+46702-161604
> > ___
> > subsurface mailing list
> > subsurface@subsurface-divelog.org
> > http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
> >
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Android app

[Jan Mulder]

On 27-08-17 08:23, Dirk Hohndel wrote:

I pushed the latest version (with quite a few Kirigami updates) to both 
downloads/test and Google Play Beta.
I'll need to redo all the screen shots. Again. But I really think the look is 
coming together.

Jocke and Jan - are you still working on the UI? There were still a few things 
that needed updates, especially the entering of credentials...


Just back from 2.5 weeks over exploratory cave diving, and just starting 
to pick up the pieces. Currently, no UI relating things done, but 
already did some cleanup related to the very confusing credential state 
processing. I feel that this needs to be done first before touching the 
UI in this area.



It would be nice to get Subsurface-mobile on Android to a stage where we feel 
good to do a release.


During my trip, I used a self built app version -719, and I like to 
share some experiences.


1) Obviously, my fellow cave explorers are impressed by the flawlessly 
working BT interfacing right after the dive :-)


2) As I always have Bluetooth off, I have to restart the app with it 
switched on in 100% of the cases. I simply forget to switch it on 
before. I will open a issue for this. Not important for every user, but 
it annoys me big time.


3) On my 5.5" phone (so not a huge device), I had problems typing in 
notes. Things get confusing when the notes are longer than the room 
available. It does not auto scroll while typing (so typing in the 
blind), it sometimes just stops editing (having to redo it), but a 
workaround for me worked. Add just a short note, save the dive and edit 
the notes in a second pass. I believe the UI/QML needs some work here.


4) I like the "autocomplete" for buddies. But something similar for 
divesites would be nice.


--jan


___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Android app

[Willem Ferguson]

Dirk,

I was out of town for a while. When you are ready for the new release, 
give me a mail (at both email adresses, please) and I will redo 
screenshots. Should not take longer than 24h.


Kind regards,
willem


On 27/08/2017 08:23, Dirk Hohndel wrote:

I pushed the latest version (with quite a few Kirigami updates) to both 
downloads/test and Google Play Beta.
I'll need to redo all the screen shots. Again. But I really think the look is 
coming together.

Jocke and Jan - are you still working on the UI? There were still a few things 
that needed updates, especially the entering of credentials...
It would be nice to get Subsurface-mobile on Android to a stage where we feel 
good to do a release.

Thanks for your help

/D
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface



___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Android app

[Dirk Hohndel]

> On Aug 28, 2017, at 6:33 AM, Jan Mulder  wrote:
> 
> On 27-08-17 08:23, Dirk Hohndel wrote:
>> I pushed the latest version (with quite a few Kirigami updates) to both 
>> downloads/test and Google Play Beta.
>> I'll need to redo all the screen shots. Again. But I really think the look 
>> is coming together.
>> Jocke and Jan - are you still working on the UI? There were still a few 
>> things that needed updates, especially the entering of credentials...
> 
> Just back from 2.5 weeks over exploratory cave diving, and just starting to 
> pick up the pieces. Currently, no UI relating things done, but already did 
> some cleanup related to the very confusing credential state processing. I 
> feel that this needs to be done first before touching the UI in this area.

No argument there.

>> It would be nice to get Subsurface-mobile on Android to a stage where we 
>> feel good to do a release.
> 
> During my trip, I used a self built app version -719, and I like to share 
> some experiences.
> 
> 1) Obviously, my fellow cave explorers are impressed by the flawlessly 
> working BT interfacing right after the dive :-)

:-)

> 2) As I always have Bluetooth off, I have to restart the app with it switched 
> on in 100% of the cases. I simply forget to switch it on before. I will open 
> a issue for this. Not important for every user, but it annoys me big time.

We had a few people express dismay over that. It shouldn't be HARD to fix, I 
think. We just need to rethink how we populate the drop downs.

> 3) On my 5.5" phone (so not a huge device), I had problems typing in notes. 
> Things get confusing when the notes are longer than the room available. It 
> does not auto scroll while typing (so typing in the blind), it sometimes just 
> stops editing (having to redo it), but a workaround for me worked. Add just a 
> short note, save the dive and edit the notes in a second pass. I believe the 
> UI/QML needs some work here.

Yes - we should just get rid of the overlay and turn this into a regular page.

> 4) I like the "autocomplete" for buddies. But something similar for divesites 
> would be nice.

Given the complexity and insanity of our dive site handling - that might be 
harder than it sounds.

The credential stuff should get fixed before we release 2.0.

The BT enabling would be need for 2.1

The dive sites... I'm guessing version 6.4 ?

/D
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Android app Improvements

[Joseph W. Joshua]

Hello all,

I’m thinking on working on some improvements on the android app, and after a 
word with Dirk he suggested a simple layout:

When you open Subsurface, all you see is the dive list. You tap on a dive, you 
see the profile. Now swiping left and right you can get to the different tabs 
on the main tab plus the map. The back key gets you back to the dive list, 
swiping up and down gets you to the previous and next dive without going to the 
dive list…

So, do we do this in QML or in QWidgets? Any Ideas? 
--
Joseph W. Joshua



___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Android APP

[Dirk Hohndel via subsurface]

You are using the beta version which is currently broken.
There are some rather frustrating interdependencies that make it extremely hard 
to rebuild the app and follow the new requirements of the Google Play store - 
so this will stay broken for a while, I'm afraid.

The simple work around is to leave the beta program and go back to the 
production app.

/D

> On Jun 1, 2023, at 05:59, Leo Ekelmans via subsurface 
>  wrote:
> 
> Dear Subsurface developpers,
> 
> I am a happy user of the subsurface programs on Android, ipad and mac book.
> Unfortunately since the latest Android update of May 27th the app is crashing 
> on my Samsung A52. Not sure if this has been reported sofar
> 
> Regards,
> Leo
> ___
> subsurface mailing list
> subsurface@subsurface-divelog.org
> http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: subsurface android app

[Dirk Hohndel]

Hallo Joachim...

> On Dec 19, 2015, at 10:34 AM, Joachim Herrmann  
> wrote:
> 
> Dear subsurface developpers, 
> I am a user of your Desktop application. Today I had the idea to use your 
> cloud-service to access my dives on my android phone. 

Excellent idea!

> SO I got myself an account and confirmed it through email. 
> After installing the app on my phone  I entered my User Id, checked that the 
> API URL is correct and did everything I could think of with the same result : 
> „no dives“. 

Here is where you went wrong, but it's not your fault.
We are working furiously on getting the new Subsurface-mobile Android app 
ready. But what you can install from the Google Play store right now, 
unfortunately, is still just our old "Companion App". All this app is designed 
to do is to store GPS locations while on a dive boat. So the web account it is 
talking about is NOT the cloud storage but a different web service that we 
developed a few years ago that simply allows you to sync GPS fixes with your 
matching dives. Very useful, but not what you are looking for.

If you are interested you could test the development version of 
Subsurface-mobile. It's still a little rough around the edges but is making 
great progress. You can download it here:

http://subsurface-divelog.org/downloads/daily/Subsurface-mobile-4.5.2.463-arm.apk
 
We'd love to hear feedback about it. On some phones, for reasons we don't 
understand, yet, the icons are just black squares. It would be useful for us to 
know if this happens to you.

All the best

/D
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Android app -755

[Jan Mulder]

On 29-01-16 08:00, Dirk Hohndel wrote:

Anyway, I'd appreciate a fresh round of testing. This should close a
number of outstanding bugs.

And I'm sure I have successfully added a few new ones in return :-)


A very quick test (on 1 5" device, running Android 6.0.1). Look pretty 
solid to me. Some observations:


1) Manual add dive, cancel the add, and the dive shows up in the 
divelist. Without ever touching the save button. Luckily it is gone 
after re-starting the app.


2) Swiping trough the dives I still sometimes get an empty profile.

3) After 5 minutes of clicking and swiping I ran into a SIGSEGV. One 
thing, I thing, that is very useful for an open beta is making sure that 
the profile does only renders (and computes) the things we want. I 
believe that this crash is coming from profile drawing, but cannot 
pinpoint at this moment.


Sizing of DiveDetails is ok on my device.

best,

--jan
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Android app -755

[David Tillotson]

On 29 January 2016 07:00:12 GMT+00:00, Dirk Hohndel  wrote:
>More poking in the dark by a blind hacker. But it seems I'm slowly
>getting
>the hang of a few things. Tomaz / Sebastian - I'd appreciate if you
>could
>look over my last dozen commits. I've done some more advanced Qt
>hacking
>(at least more advanced than my usual dabbling) in commit af9f07626a01
>and
>used that in the following commits to be able to actually poke at the
>data
>in the model (which made things so much simpler for me). This still
>isn't
>perfect, I can still get to a point where I'm not highlighting the
>correct
>dive, but it seems much more reliable.
>
>I also dealt with more weird layout issues and appear to have figured
>out
>a clean way to know how wide a column is supposed to be. Sebastian, I'd
>appreciate if you could take a look at that in commit ba4bb5670192.
>This
>does recreate code that's in PageRow.qml, but I didn't manage to
>reliably
>extract the columnWidth variable from there whereas this way seems to
>be
>easy and accessible from anywhere in the code.
>
>Anyway, I'd appreciate a fresh round of testing. This should close a
>number of outstanding bugs.
>
>And I'm sure I have successfully added a few new ones in return :-)
>
>/D
>___
>subsurface mailing list
>subsurface@subsurface-divelog.org
>http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

With the latest from the dailies on the site (to answer a previous question), I 
get consistent sizing on the screen. The edit button still seems to have random 
success - I have been trying to identify a pattern, but can't find one. The 
same happens with the cancel button, so it's likely that the press isn't being 
picked up. I'll try a clean installation and get back on this.
I've also found that some of my log entries reliably crash the app. They're all 
at the same site (local quarry used for training), so I suspect an oddity in 
the location data. I'll check the data on the laptop this evening. As an aside, 
is there a way to directly access the files on Android?
-- 
David Tillotson
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Android app -755

[Dirk Hohndel]

On Fri, Jan 29, 2016 at 09:11:26AM +0100, Jan Mulder wrote:
> On 29-01-16 08:00, Dirk Hohndel wrote:
> >Anyway, I'd appreciate a fresh round of testing. This should close a
> >number of outstanding bugs.
> >
> >And I'm sure I have successfully added a few new ones in return :-)
> 
> A very quick test (on 1 5" device, running Android 6.0.1). Look pretty solid
> to me. Some observations:
> 
> 1) Manual add dive, cancel the add, and the dive shows up in the divelist.
> Without ever touching the save button. Luckily it is gone after re-starting
> the app.

Yes, and I know exactly why. The change to avoid re-reading all the dives
(which caused the app to render every single profile) caused this. I'll
fix that.

> 2) Swiping trough the dives I still sometimes get an empty profile.

Yes, I had that yesterday. I believe this is caused by our somewhat
asynchronous way of drawing the profile. Basically when you we set the
dive, all we do is we tell the profile which dive it is supposed to draw.
Then the profile "draws itself". Which is really nice and all in the
desktop app because you don't need to worry about it. But in
Subsurface-mobile we then paint the profile to a pixmap and show that
pixmap. And if we do that before the profile was finished rearranging
itself, we paint an empty pixmap. Or sometimes one that has only part of
the depth / time grid drawn.

I keep thinking of a way to avoid this - but as it works "most of the
time" it hasn't bubbled to my top priorities, yet.

> 3) After 5 minutes of clicking and swiping I ran into a SIGSEGV. One thing,

I assume you don't have a stack trace for that, do you?

> I thing, that is very useful for an open beta is making sure that the
> profile does only renders (and computes) the things we want. I believe that
> this crash is coming from profile drawing, but cannot pinpoint at this
> moment.

I'm not sure what you mean by "only renders (and computes) the things we
want". Can you explain a bit more?

> Sizing of DiveDetails is ok on my device.

Good.

/D
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Android app -755

[Jan Mulder]

On 29-01-16 15:01, Dirk Hohndel wrote:

On Fri, Jan 29, 2016 at 09:11:26AM +0100, Jan Mulder wrote:

2) Swiping trough the dives I still sometimes get an empty profile.

Yes, I had that yesterday. I believe this is caused by our somewhat
asynchronous way of drawing the profile. Basically when you we set the
dive, all we do is we tell the profile which dive it is supposed to draw.
Then the profile "draws itself". Which is really nice and all in the
desktop app because you don't need to worry about it. But in
Subsurface-mobile we then paint the profile to a pixmap and show that
pixmap. And if we do that before the profile was finished rearranging
itself, we paint an empty pixmap. Or sometimes one that has only part of
the depth / time grid drawn.

I keep thinking of a way to avoid this - but as it works "most of the
time" it hasn't bubbled to my top priorities, yet.
Agree that this is not a very high priority thing, and your hypothesis 
sounds plausible.



3) After 5 minutes of clicking and swiping I ran into a SIGSEGV. One thing,

I assume you don't have a stack trace for that, do you?
In fact, I do have a full tombstone on this. The contents is, however, 
not very interesting. A very tiny fragment:


Build fingerprint: 
'Wileyfox/Swift/crackling:6.0.1/MMB29T/29bf0bab96:userdebug/test-keys'
Revision: '0'
ABI: 'arm'
pid: 8435, tid: 8449, name: QtThread  >>> org.subsurfacedivelog.mobile <<<
signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 0xe0502fdc

[snip]

 backtrace:
#00 pc 00017b90  /system/lib/libm.so (pow)
#01 pc 0281816c  [heap]


Further, as you probably have seen, the logcat is full of warnings saying:

01-29 08:31:01.801  8435  8457 W Subsurface: (null):0 ((null)): 
QObject::startTimer: Timers cannot be started from another thread

Somehow, this sounds suspicious, but might well be a Mobilecomponents or Qt/QML 
thing.


I thing, that is very useful for an open beta is making sure that the
profile does only renders (and computes) the things we want. I believe that
this crash is coming from profile drawing, but cannot pinpoint at this
moment.

I'm not sure what you mean by "only renders (and computes) the things we
want". Can you explain a bit more?
As on IRC, the profile drawing seems very dive profile length dependent 
in the sense of performance. Currently, this is not a real problem for 
most users, as they are doing relatively short (in my vocabulary) dives. 
However, all unnecessary processing not only slows things down, but can 
also have a negative impact on stability, or even prevent usable crash 
stacks. So my philosophy here is: less processing is better. Not sure 
how easy it is to suppress the numerous options as available in the 
desktop software with respect to profile drawing, but it might be a 
"quick fix" for performance or stability on the mobile app. best, --jan
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Android app -755

[Dirk Hohndel]

On Fri, Jan 29, 2016 at 04:23:36PM +0100, Jan Mulder wrote:
> >I keep thinking of a way to avoid this - but as it works "most of the
> >time" it hasn't bubbled to my top priorities, yet.
> Agree that this is not a very high priority thing, and your hypothesis
> sounds plausible.

I still want to go through the profile code and see if we can make it
faster / make sure all the options that could slow it down are disabled.

> >>3) After 5 minutes of clicking and swiping I ran into a SIGSEGV. One thing,
> >I assume you don't have a stack trace for that, do you?
> In fact, I do have a full tombstone on this. The contents is, however, not
> very interesting. A very tiny fragment:
> 
> Build fingerprint: 
> 'Wileyfox/Swift/crackling:6.0.1/MMB29T/29bf0bab96:userdebug/test-keys'
> Revision: '0'
> ABI: 'arm'
> pid: 8435, tid: 8449, name: QtThread  >>> org.subsurfacedivelog.mobile <<<
> signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 0xe0502fdc
> 
> [snip]
> 
>  backtrace:
> #00 pc 00017b90  /system/lib/libm.so (pow)
> #01 pc 0281816c  [heap]

Yeah, not really helpful.
And once again the current calgrind / valgrind is broken and can't deal
with Subsurface, so this is even harder to test. Julian is aware of this
and working on a fix...

> Further, as you probably have seen, the logcat is full of warnings saying:
> 
> 01-29 08:31:01.801  8435  8457 W Subsurface: (null):0 ((null)): 
> QObject::startTimer: Timers cannot be started from another thread
> 
> Somehow, this sounds suspicious, but might well be a Mobilecomponents or 
> Qt/QML thing.

This is on my list of things I'm trying to track down and always get lost
in the weeds. Definitely ominous.

> >>I thing, that is very useful for an open beta is making sure that the
> >>profile does only renders (and computes) the things we want. I believe that
> >>this crash is coming from profile drawing, but cannot pinpoint at this
> >>moment.
> >I'm not sure what you mean by "only renders (and computes) the things we
> >want". Can you explain a bit more?
> As on IRC, the profile drawing seems very dive profile length dependent in
> the sense of performance. Currently, this is not a real problem for most
> users, as they are doing relatively short (in my vocabulary) dives. However,
> all unnecessary processing not only slows things down, but can also have a
> negative impact on stability, or even prevent usable crash stacks. So my
> philosophy here is: less processing is better. Not sure how easy it is to
> suppress the numerous options as available in the desktop software with
> respect to profile drawing, but it might be a "quick fix" for performance or
> stability on the mobile app. best, 

Oh yes, I 100% agree. This would be a great project for someone to dive
into because it will take some time to read the code, understand what we
do and make sure everything and anything that we can avoid has been either
turned off or maybe even compiled out.

/D
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Android app -755

[Lubomir I. Ivanov]

On 29 January 2016 at 17:23, Jan Mulder  wrote:
> 3) After 5 minutes of clicking and swiping I ran into a SIGSEGV. One thing,

is there some sort of a consistency in the crash location - dive #,
sequence of events etc?
can this be reproduced on each run?

> ABI: 'arm'
> pid: 8435, tid: 8449, name: QtThread  >>> org.subsurfacedivelog.mobile <<<
> signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 0xe0502fdc
>
> [snip]
>
>  backtrace:
> #00 pc 00017b90  /system/lib/libm.so (pow)
> #01 pc 0281816c  [heap]
>

a SIGSEGV inside pow() is plain odd.

it's implementation dependent, but some of the math.h functions can
use a bunch of tricks like logx() lookup tables, taylor series
approximations with range reduction, mantissa exponent separation and
so on. if the crash is really inside pow() then it must to be fed a
very bogus value that bypasses some of the error checks (that i'm sure
are present in libm) and accesses a lookup table index out of range.
then, that out of range index should be large enough to even throw a
SIGSEGV, as it could sometimes just work with adjacent memory and
return something like 0.00.

now, the backtrace could be just wrong and the actual bogus access
could be outside of pow() - i.e. in the function input.
grepping for usage of pow() in subsurface i don't see anything that suspicious.
deco.c (is buehlmann_N2_t_halflife[ci] safe?), divelist.c, etc.

this bug requires some plain stderr/stdout debugging to catch the
exact offending stage.

lubomir
--
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Android app -755

[Dirk Hohndel]

On Fri, Jan 29, 2016 at 07:09:03PM +0200, Lubomir I. Ivanov wrote:
> On 29 January 2016 at 17:23, Jan Mulder  wrote:
> > 3) After 5 minutes of clicking and swiping I ran into a SIGSEGV. One thing,
> 
> is there some sort of a consistency in the crash location - dive #,
> sequence of events etc?
> can this be reproduced on each run?
> 
> > ABI: 'arm'
> > pid: 8435, tid: 8449, name: QtThread  >>> org.subsurfacedivelog.mobile <<<
> > signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 0xe0502fdc
> >
> > [snip]
> >
> >  backtrace:
> > #00 pc 00017b90  /system/lib/libm.so (pow)
> > #01 pc 0281816c  [heap]
> >
> 
> a SIGSEGV inside pow() is plain odd.
> 
> it's implementation dependent, but some of the math.h functions can
> use a bunch of tricks like logx() lookup tables, taylor series
> approximations with range reduction, mantissa exponent separation and
> so on. if the crash is really inside pow() then it must to be fed a
> very bogus value that bypasses some of the error checks (that i'm sure
> are present in libm) and accesses a lookup table index out of range.
> then, that out of range index should be large enough to even throw a
> SIGSEGV, as it could sometimes just work with adjacent memory and
> return something like 0.00.
> 
> now, the backtrace could be just wrong and the actual bogus access
> could be outside of pow() - i.e. in the function input.
> grepping for usage of pow() in subsurface i don't see anything that 
> suspicious.
> deco.c (is buehlmann_N2_t_halflife[ci] safe?), divelist.c, etc.
> 
> this bug requires some plain stderr/stdout debugging to catch the
> exact offending stage.

I was also suspecting that it might be something in the deco calculation.
And given that we don't expose the ability to display the calculated
ceiling or the TTS or anything else... I would really like to see a patch
that just compiles out all that code when building Subsurface-mobile.

I realize that there are some tech divers who disagree with this and who
instead want the ability to show ceilings - maybe we'll do a
Subsurface-mobile (tech edition) for those and tell them "hey, it may
crash and it WILL be slow".

/D
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Android app -755

[Rick Walsh]

On 30 Jan 2016 04:26, "Dirk Hohndel"  wrote:
>
> I was also suspecting that it might be something in the deco calculation.
> And given that we don't expose the ability to display the calculated
> ceiling or the TTS or anything else... I would really like to see a patch
> that just compiles out all that code when building Subsurface-mobile.
>
> I realize that there are some tech divers who disagree with this and who
> instead want the ability to show ceilings - maybe we'll do a
> Subsurface-mobile (tech edition) for those and tell them "hey, it may
> crash and it WILL be slow".
>
I'm a tech diver, but it seems I'm not one of 'those' tech divers. I'll
take a snappy and stable mobile app any day over one that calculates and
displays the ceiling after the dive has happened. It's a feature I like on
the desktop, but can live without on my phone.

But, can I put in my request now to have the dc reported ceiling where it
exists? Hopefully not too difficult, and won't require deco calculations.

(I've got too much on at the moment to take the bait and submit the patch
you're asking for)

Rick
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Android app -755

[Henrik Brautaset Aronsen]

On Sat, Jan 30, 2016 at 12:14 PM, Rick Walsh  wrote:
>
> On 30 Jan 2016 04:26, "Dirk Hohndel"  wrote:
> >
> > I realize that there are some tech divers who disagree with this and who
> > instead want the ability to show ceilings - maybe we'll do a
> > Subsurface-mobile (tech edition) for those and tell them "hey, it may
> > crash and it WILL be slow".
> >
> I'm a tech diver, but it seems I'm not one of 'those' tech divers. I'll
> take a snappy and stable mobile app any day over one that calculates and
> displays the ceiling after the dive has happened. It's a feature I like on
> the desktop, but can live without on my phone.
>

I'm also a tech diver, and I *really* like the after-the-fact calculated
ceilings. But I don't need it on the phone if that makes things™ difficult.

But a planner would be really nice!  I wouldn't need the graphical version,
 just table input & output would be awesome.  No hurry, though, let's get
this baby ready to ship without too many features first :)

Henrik
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Android app -755

[Rick Walsh]

On 31 Jan 2016 01:44, "Henrik Brautaset Aronsen" 
wrote:
>
> On Sat, Jan 30, 2016 at 12:14 PM, Rick Walsh  wrote:
>>
>> On 30 Jan 2016 04:26, "Dirk Hohndel"  wrote:
>> >
>> > I realize that there are some tech divers who disagree with this and
who
>> > instead want the ability to show ceilings - maybe we'll do a
>> > Subsurface-mobile (tech edition) for those and tell them "hey, it may
>> > crash and it WILL be slow".
>> >
>> I'm a tech diver, but it seems I'm not one of 'those' tech divers. I'll
take a snappy and stable mobile app any day over one that calculates and
displays the ceiling after the dive has happened. It's a feature I like on
the desktop, but can live without on my phone.
>
>
> I'm also a tech diver, and I *really* like the after-the-fact calculated
ceilings. But I don't need it on the phone if that makes things™ difficult.
>
> But a planner would be really nice!  I wouldn't need the graphical
version,  just table input & output would be awesome.  No hurry, though,
let's get this baby ready to ship without too many features first :)
>
I have a working ui for a simple planner. But sorting out how to connect
the background code is proving harder than I'd hoped. I want to use the
existing qt-models but it's proving not so straightforward for someone with
no prior knowledge of qt.

I'm holding off submitting the patches so as not to distract from getting
the first release out. Hopefully by that time I'll have worked it out, or
more likely someone will see straight away how to make the planner plan
then.

Rick
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Android app -755

[Lubomir I. Ivanov]

On 29 January 2016 at 19:26, Dirk Hohndel  wrote:
> On Fri, Jan 29, 2016 at 07:09:03PM +0200, Lubomir I. Ivanov wrote:
>> On 29 January 2016 at 17:23, Jan Mulder  wrote:
>> > 3) After 5 minutes of clicking and swiping I ran into a SIGSEGV. One thing,
>>
>> is there some sort of a consistency in the crash location - dive #,
>> sequence of events etc?
>> can this be reproduced on each run?
>>

waiting on Jan to respond so that we can have a better guess.

>> > ABI: 'arm'
>> > pid: 8435, tid: 8449, name: QtThread  >>> org.subsurfacedivelog.mobile <<<
>> > signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 0xe0502fdc
>> >
>> > [snip]
>> >
>> >  backtrace:
>> > #00 pc 00017b90  /system/lib/libm.so (pow)
>> > #01 pc 0281816c  [heap]
>> >
>>
>> a SIGSEGV inside pow() is plain odd.
>>
>> it's implementation dependent, but some of the math.h functions can
>> use a bunch of tricks like logx() lookup tables, taylor series
>> approximations with range reduction, mantissa exponent separation and
>> so on. if the crash is really inside pow() then it must to be fed a
>> very bogus value that bypasses some of the error checks (that i'm sure
>> are present in libm) and accesses a lookup table index out of range.
>> then, that out of range index should be large enough to even throw a
>> SIGSEGV, as it could sometimes just work with adjacent memory and
>> return something like 0.00.
>>
>> now, the backtrace could be just wrong and the actual bogus access
>> could be outside of pow() - i.e. in the function input.
>> grepping for usage of pow() in subsurface i don't see anything that 
>> suspicious.
>> deco.c (is buehlmann_N2_t_halflife[ci] safe?), divelist.c, etc.
>>
>> this bug requires some plain stderr/stdout debugging to catch the
>> exact offending stage.
>
> I was also suspecting that it might be something in the deco calculation.
> And given that we don't expose the ability to display the calculated
> ceiling or the TTS or anything else... I would really like to see a patch
> that just compiles out all that code when building Subsurface-mobile.

it can also be one of the calls from divelist.c breaking on a certain
weird ARM pow() implementation.

the main problem with the mobile version crash reports ATM seems to be
not so useful backtraces.
a verbose build of the mobile version that shows a bunch of print() /
console.log() message is going to be very useful.

it would be then much easier to narrow down problematic stages.

lubomir
--
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Android app -755

[Jan Mulder]

On 30-01-16 21:07, Lubomir I. Ivanov wrote:

On 29 January 2016 at 17:23, Jan Mulder  wrote:

3) After 5 minutes of clicking and swiping I ran into a SIGSEGV. One thing,

is there some sort of a consistency in the crash location - dive #,
sequence of events etc?
can this be reproduced on each run?

waiting on Jan to respond so that we can have a better guess.


I have seen this "pow() crash" once, and I have not been able to 
reproduce (despite trying). So, at this point in time, I suggest not to 
give this one a high priority. Especially given the very weird stack 
trace. That said, I can also not reproduce the crash as reported by 
Willem (on 5.1.1 and 6.0.1).





a SIGSEGV inside pow() is plain odd.

Fully agree on this.


the main problem with the mobile version crash reports ATM seems to be
not so useful backtraces.
It is a little hit and miss. Sometimes the crash stacks are pointing in 
the right direction, but, for example, this "pow crash" is extremely 
difficult to judge.



a verbose build of the mobile version that shows a bunch of print() /
console.log() message is going to be very useful. it would be then much easier 
to narrow down problematic stages.
Sure this would help, but there is a lot a closely related QT and QML 
stuff that is a little suspicious, and the execution path of QML is not 
cristal clear for most of us (and I am afraid that this is a strong 
understatement). So even console-logging is not straightforward to 
interpret.


best.

--jan
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Android app -923

[Sebastian Kügler]

On Thursday, March 03, 2016 03:22:40 PM Dirk Hohndel wrote:
> Sebas, now that we are on Qt 5.6... do you remember what you and I tested
> a couple of months ago with getting the correct keyboard geometry from Qt?
> I know that worked with 5.6... so maybe you could create a Kirigami patch
> to use that data so the users don't need to close the keyboard to access
> the bottom part of a page?

Yep, I remember. I'll try to get to it in the next week, but can't promise 
since we have a sprint.

Cheers,
-- 
sebas

http://www.kde.org | http://vizZzion.org
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Android app Improvements

[Tomaz Canabrava]

Joseph

In qml this is easier ( swipe)  but we May need to change a few things on
the software.

Id go for qml on mobile platforms,  and if you hit any wall I can help
change the code só it works on mobile and desktop.

Em 30/12/2014 01:56, "Joseph W. Joshua"  escreveu:
>
> Hello all,
>
> I’m thinking on working on some improvements on the android app, and
after a word with Dirk he suggested a simple layout:
>
> When you open Subsurface, all you see is the dive list. You tap on a
dive, you see the profile. Now swiping left and right you can get to the
different tabs on the main tab plus the map. The back key gets you back to
the dive list, swiping up and down gets you to the previous and next dive
without going to the dive list…
>
> So, do we do this in QML or in QWidgets? Any Ideas?
> --
> Joseph W. Joshua
>
>
>
> ___
> subsurface mailing list
> subsurface@subsurface-divelog.org
> http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Android app Improvements

[Joseph W. Joshua]

> On Dec 30, 2014, at 2:53 PM, Tomaz Canabrava  wrote:
> 
> Joseph
> 
> In qml this is easier ( swipe)  but we May need to change a few things on the 
> software.
> 
> Id go for qml on mobile platforms,  and if you hit any wall I can help change 
> the code só it works on mobile and desktop. 
> 
> 
> 
Ok, Tomaz,

I will work on a basic concept.
> >
> >
> >
> > ___
> > subsurface mailing list
> > subsurface@subsurface-divelog.org 
> > http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface 
> > 

___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Android app Improvements

[Dirk Hohndel]

On Tue, Dec 30, 2014 at 09:53:30AM -0200, Tomaz Canabrava wrote:
> Joseph
> 
> In qml this is easier ( swipe)  but we May need to change a few things on
> the software.
> 
> Id go for qml on mobile platforms,  and if you hit any wall I can help
> change the code só it works on mobile and desktop.

I would, however, prefer if we kept the QML dependency to be on the mobile
app, only.

/D
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Question about the android app

[Martin Fuhr]

Hello subsurface-team,

with the change from Aladdin Air Z Nitrox to Galileo Sol there was also a 
change from an old version of wlog (runing on my old windows xp netbook) to the 
newest version of subsurface. I like this type of logbook software on my vista 
machine and via sync on my linux machine.
I have a question about the android support app:
Is it possible to use the app for more then saving the current GPS data??? It 
would be a great benefit for me to read my divecomputer, editing older dives 
and sync to the "cloud" on location... (in the same way like the desktop 
version)

With the best wishes for the new year...
Greetings from Bavaria/Germany

Martin
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: subsurface android app coordinates database

[Willem Ferguson]

>From my phone. I just downloaded the most recent subsurface mobile. After
dowloading dives from the cloud, in the logfile it says " number of GPS
fixes = 0. But there should be some 30 GPS locations on the locations
server. Is this an error?
Kind regards, willem
On 19 Dec 2015 20:45, "Dirk Hohndel"  wrote:

> Hallo Joachim...
>
> > On Dec 19, 2015, at 10:34 AM, Joachim Herrmann <
> martinaundjoc...@outlook.de> wrote:
> >
> > Dear subsurface developpers,
> > I am a user of your Desktop application. Today I had the idea to use
> your cloud-service to access my dives on my android phone.
>
> Excellent idea!
>
> > SO I got myself an account and confirmed it through email.
> > After installing the app on my phone  I entered my User Id, checked that
> the API URL is correct and did everything I could think of with the same
> result : „no dives“.
>
> Here is where you went wrong, but it's not your fault.
> We are working furiously on getting the new Subsurface-mobile Android app
> ready. But what you can install from the Google Play store right now,
> unfortunately, is still just our old "Companion App". All this app is
> designed to do is to store GPS locations while on a dive boat. So the web
> account it is talking about is NOT the cloud storage but a different web
> service that we developed a few years ago that simply allows you to sync
> GPS fixes with your matching dives. Very useful, but not what you are
> looking for.
>
> If you are interested you could test the development version of
> Subsurface-mobile. It's still a little rough around the edges but is making
> great progress. You can download it here:
>
>
> http://subsurface-divelog.org/downloads/daily/Subsurface-mobile-4.5.2.463-arm.apk
>
> We'd love to hear feedback about it. On some phones, for reasons we don't
> understand, yet, the icons are just black squares. It would be useful for
> us to know if this happens to you.
>
> All the best
>
> /D
> ___
> subsurface mailing list
> subsurface@subsurface-divelog.org
> http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
>
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: subsurface android app coordinates database

[Dirk Hohndel]

IIRC I haven't implemented the download, yet. Just the upload. On my todo list. 

/D

-- 
Sent from my phone

> On Dec 19, 2015, at 11:13, Willem Ferguson  
> wrote:
> 
> From my phone. I just downloaded the most recent subsurface mobile. After 
> dowloading dives from the cloud, in the logfile it says " number of GPS fixes 
> = 0. But there should be some 30 GPS locations on the locations server. Is 
> this an error?
> Kind regards, willem
> 
>> On 19 Dec 2015 20:45, "Dirk Hohndel"  wrote:
>> Hallo Joachim...
>> 
>> > On Dec 19, 2015, at 10:34 AM, Joachim Herrmann 
>> >  wrote:
>> >
>> > Dear subsurface developpers,
>> > I am a user of your Desktop application. Today I had the idea to use your 
>> > cloud-service to access my dives on my android phone.
>> 
>> Excellent idea!
>> 
>> > SO I got myself an account and confirmed it through email.
>> > After installing the app on my phone  I entered my User Id, checked that 
>> > the API URL is correct and did everything I could think of with the same 
>> > result : „no dives“.
>> 
>> Here is where you went wrong, but it's not your fault.
>> We are working furiously on getting the new Subsurface-mobile Android app 
>> ready. But what you can install from the Google Play store right now, 
>> unfortunately, is still just our old "Companion App". All this app is 
>> designed to do is to store GPS locations while on a dive boat. So the web 
>> account it is talking about is NOT the cloud storage but a different web 
>> service that we developed a few years ago that simply allows you to sync GPS 
>> fixes with your matching dives. Very useful, but not what you are looking 
>> for.
>> 
>> If you are interested you could test the development version of 
>> Subsurface-mobile. It's still a little rough around the edges but is making 
>> great progress. You can download it here:
>> 
>> http://subsurface-divelog.org/downloads/daily/Subsurface-mobile-4.5.2.463-arm.apk
>> 
>> We'd love to hear feedback about it. On some phones, for reasons we don't 
>> understand, yet, the icons are just black squares. It would be useful for us 
>> to know if this happens to you.
>> 
>> All the best
>> 
>> /D
>> ___
>> subsurface mailing list
>> subsurface@subsurface-divelog.org
>> http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
> ___
> subsurface mailing list
> subsurface@subsurface-divelog.org
> http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Question about the android app

[Dirk Hohndel]

On Thu, Jan 07, 2016 at 09:24:54PM +0100, Martin Fuhr wrote:
> Hello subsurface-team,
> 
> with the change from Aladdin Air Z Nitrox to Galileo Sol there was also a 
> change from an old version of wlog (runing on my old windows xp netbook) to 
> the newest version of subsurface. I like this type of logbook software on my 
> vista machine and via sync on my linux machine.
> I have a question about the android support app:
> Is it possible to use the app for more then saving the current GPS data??? It 
> would be a great benefit for me to read my divecomputer, editing older dives 
> and sync to the "cloud" on location... (in the same way like the desktop 
> version)

We are well on our way working on a completely new Android app.

In its current state it allows you to

a) connect to the cloud storage to access your dive list
b) edit dives in that list
c) manually add dives to that list
d) record and apply GPS fixes

The one thing on your wish list we don't have, yet, is directly
downloading from dive computers. We have plans to add that, but so far
none of the developers have had the time to implement and test that.

That said... Galileo Sol is iRDA based, correct? That will never be
supported on Android, isn't supported on Mac and Windows 10. So that may
not be a great choice if downloading to the Android device is what you
want to be able to do. Our current expectation is that we'll be able to
support BT based dive computers and some dive computers that have download
mechanisms that are based on FTDI chips (e.g. the OSTC dive computers).

Hope this helps

/D
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Question about the android app

[Willem Ferguson]

On 07/01/2016 23:22, Dirk Hohndel wrote:


We are well on our way working on a completely new Android app.

In its current state it allows you to

a) connect to the cloud storage to access your dive list
b) edit dives in that list
c) manually add dives to that list
d) record and apply GPS fixes

The one thing on your wish list we don't have, yet, is directly
downloading from dive computers. We have plans to add that, but so far
none of the developers have had the time to implement and test that.

That said... Galileo Sol is iRDA based, correct? That will never be
supported on Android, isn't supported on Mac and Windows 10. So that may
not be a great choice if downloading to the Android device is what you
want to be able to do. Our current expectation is that we'll be able to
support BT based dive computers and some dive computers that have download
mechanisms that are based on FTDI chips (e.g. the OSTC dive computers).

Hope this helps

/D
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
See the URL below. Owning a Galileo myself, I was intrigued by the guys 
below who appear to use a "normal" USB OTG connection and a Uwatec IR 
adapter to read the dives from a Sol into Android. I assume they must 
have found some way to implement an IrDA stack in Android? Dirk, with 
your German connections, would you be able to obtain more information?


https://play.google.com/store/apps/details?id=com.confitek.divemateusb

Kind regards,
willem

___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Subsurface-mobile Android app profile scaling

[Dirk Hohndel]

Maybe we have been trying too hard? 

After playing with various options for several hours over the last few days and 
staring at tons and tons of debug output I tried something different and so far 
it looks like it might work. This has only been tested natively on Linux and on 
two Android phones, but so far, so good.

Latest APK (675) is on dailies, should make it through Google Play store soon. 
Please test and report.

Sebastian - please look at my commit 464b88f01 and tell me if you think this is 
reasonable...

Thanks

/D

___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Subsurface-mobile Android app profile scaling

[Rick Walsh]

On 19 Jan 2016 08:16, "Dirk Hohndel"  wrote:
>
> Maybe we have been trying too hard?
>
> After playing with various options for several hours over the last few
days and staring at tons and tons of debug output I tried something
different and so far it looks like it might work. This has only been tested
natively on Linux and on two Android phones, but so far, so good.
>
> Latest APK (675) is on dailies, should make it through Google Play store
soon. Please test and report.
>
At last, something that works (for me) and with code that looks logical too!

Tested on a galaxy s6 with a good number of dives in range 13 to 85 min and
depth 5m to 45m.

Rick
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Subsurface-mobile Android app profile scaling

[Sebastian Kügler]

On Monday, January 18, 2016 13:15:54 Dirk Hohndel wrote:
> Maybe we have been trying too hard? 
> 
> After playing with various options for several hours over the last few days
> and staring at tons and tons of debug output I tried something different
> and so far it looks like it might work. This has only been tested natively
> on Linux and on two Android phones, but so far, so good.
> 
> Latest APK (675) is on dailies, should make it through Google Play store
> soon. Please test and report.
> 
> Sebastian - please look at my commit 464b88f01 and tell me if you think this
> is reasonable...

Pff, seriously?

We may indeed have been trying too hard. The code looks good, if it produces 
good results, it *is* good. (I haven't tried yet, I'm at a company meeting 
this week with little to no time left, neither for subsurface, nor for diving. 
:P)

Thanks a lot for being stubborn about this issue, Dirk!
-- 
sebas

Sebastian Kügler|http://vizZzion.org| http://kde.org

___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

RE: Subsurface-mobile Android app profile scaling

[John Smith]

Tested on 5.1 on hudl tablet and looks much better.


From: subsurface [subsurface-boun...@subsurface-divelog.org] on behalf of Dirk 
Hohndel [d...@hohndel.org]
Sent: 18 January 2016 21:15
To: Subsurface Mailing List
Subject: Subsurface-mobile Android app profile scaling

Maybe we have been trying too hard?

After playing with various options for several hours over the last few days and 
staring at tons and tons of debug output I tried something different and so far 
it looks like it might work. This has only been tested natively on Linux and on 
two Android phones, but so far, so good.

Latest APK (675) is on dailies, should make it through Google Play store soon. 
Please test and report.

Sebastian - please look at my commit 464b88f01 and tell me if you think this is 
reasonable...

Thanks

/D

___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

RE: Subsurface-mobile Android app profile scaling

[John Smith]

Actually, just nosticed that the weight value is empty in all my dives.

From: subsurface [subsurface-boun...@subsurface-divelog.org] on behalf of Dirk 
Hohndel [d...@hohndel.org]
Sent: 18 January 2016 21:15
To: Subsurface Mailing List
Subject: Subsurface-mobile Android app profile scaling

Maybe we have been trying too hard?

After playing with various options for several hours over the last few days and 
staring at tons and tons of debug output I tried something different and so far 
it looks like it might work. This has only been tested natively on Linux and on 
two Android phones, but so far, so good.

Latest APK (675) is on dailies, should make it through Google Play store soon. 
Please test and report.

Sebastian - please look at my commit 464b88f01 and tell me if you think this is 
reasonable...

Thanks

/D

___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Subsurface-mobile Android app profile scaling

[Sebastian Kügler]

On Monday, January 18, 2016 22:45:19 John Smith wrote:
> Actually, just nosticed that the weight value is empty in all my dives.

That's a different problem and  unrelated to this change.

It changed to a list of values at some point, which I didn't know how to 
interpret, probably just a small fix.
-- 
sebas

Sebastian Kügler|http://vizZzion.org| http://kde.org

___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Subsurface-mobile Android app profile scaling

[Dirk Hohndel]

> On Jan 18, 2016, at 3:01 PM, Sebastian Kügler  wrote:
> 
> On Monday, January 18, 2016 22:45:19 John Smith wrote:
>> Actually, just nosticed that the weight value is empty in all my dives.
> 
> That's a different problem and  unrelated to this change.
> 
> It changed to a list of values at some point, which I didn't know how to 
> interpret, probably just a small fix.

One thing that I noticed is that editing dives has gone haywire since the 
changes that allow the side swiping.
In landscape mode I frequently only see the keyboard plus a white screen. In 
portrait mode it seems like there are two tiles above each other (so I can see 
"something" in the background when trying to scroll the input fields so I can 
see what I do) and again I can't quite get it to work right. It's hard to 
describe, but maybe if you'll just try it you'll run into the same issues? Or I 
could make a video, I guess.

/D

___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Subsurface-mobile Android app profile scaling

[Sebastian Kügler]

On Monday, January 18, 2016 15:12:06 Dirk Hohndel wrote:
> > On Jan 18, 2016, at 3:01 PM, Sebastian Kügler  wrote:
> >
> > On Monday, January 18, 2016 22:45:19 John Smith wrote:
> >> Actually, just nosticed that the weight value is empty in all my dives.
> >
> > That's a different problem and  unrelated to this change.
> >
> > It changed to a list of values at some point, which I didn't know how to 
> > interpret, probably just a small fix.
> 
> One thing that I noticed is that editing dives has gone haywire since the
> changes that allow the side swiping. In landscape mode I frequently only
> see the keyboard plus a white screen. In portrait mode it seems like there
> are two tiles above each other (so I can see "something" in the background
> when trying to scroll the input fields so I can see what I do) and again I
> can't quite get it to work right. It's hard to describe, but maybe if
> you'll just try it you'll run into the same issues? Or I could make a
> video, I guess.

Let's have a look at this last week, sounds easy to spot.
-- 
sebas

Sebastian Kügler|http://vizZzion.org| http://kde.org

___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: count down to Beta 1 - Android app

[Joakim Bygdell]

Had a spin with the latest build, and some things stands out….

Menu -> view log, what log? seems a bit unspecific since subsurface is a dive 
log application.

Main view.
The message are need to be removed, for development it’s ok but not in the 
final version.

DiveDetail view.
The button to hide the profile.. Why??
The profile needs to span the width of the screen, currently adding a width 
specification have no effect
so in order to make the profile big enough the height needs to be set at 75% of 
the screen width since the ratio is fixed at 4:3.
Also it needs to be able to scroll or the last lines of the notes will not be 
readable, 
it becomes really apparent when the profile is enlarged to fill the screen 
width.

/Jocke

___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: count down to Beta 1 - Android app

[Grace Karanja]

‎Hi Joakim,

I intended the log feature to display some sort of application log. I guess if 
the name has some confusion we can change it.

Meanwhile I will look at the other comments regarding the dive details view.

Sent from my phone.
  Original Message  
From: Joakim Bygdell‎
Had a spin with the latest build, and some things stands out….

Menu -> view log, what log? seems a bit unspecific since subsurface is a dive 
log application.

Main view.
The message are need to be removed, for development it’s ok but not in the 
final version.

DiveDetail view.
The button to hide the profile.. Why??
The profile needs to span the width of the screen, currently adding a width 
specification have no effect
so in order to make the profile big enough the height needs to be set at 75% of 
the screen width since the ratio is fixed at 4:3.
Also it needs to be able to scroll or the last lines of the notes will not be 
readable, 
it becomes really apparent when the profile is enlarged to fill the screen 
width.

/Jocke‎
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: count down to Beta 1 - Android app

[Dirk Hohndel]

On Wed, Sep 02, 2015 at 09:35:47PM +0300, Grace Karanja wrote:
> 
> I intended the log feature to display some sort of application log. I guess 
> if the name has some confusion we can change it.
> 
> Meanwhile I will look at the other comments regarding the dive details view.

Hi Grace,

quick check in... I don't see any recent work in your devel branch on
Github. I was kinda hoping to have people start playing with the Android
App, soon, but I don't think what we have now really is ready for that.

What do you think?

I was really hoping to have at least "some" downloads from dive computers
working (that's more a request for Anton, I guess), but I also think that
the Android UI right now is still rather "klunky".

Basically I think this is a killer app, but I don't want to get people
excited, have them try and then say "wow, that UI is terrible"...

It's hard for me to get a good feeling for how much time you'll be able to
spend on this in the next few days / weeks. I understand that real life
comes first, this is not intended to put pressure on you - this email's
intention is to help me do a better job planning the next steps.

Thanks

/D
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

[PATCH] start making the android app more mobile friendly.

[Joakim Bygdell]

0001: Moves the buttons to a popup menu accessible from a single button, as 
they don’t fit on the screen of a phone.
0002: Change the background to the same blue as in the icon.
0003: Add the name to the top row of the UI.
0004: Style the menu button to fit the theme.




0001-QML-UI-create-menu-to-house-the-buttons.patch
Description: Binary data


0002-QML-UI-make-the-app-blue.patch
Description: Binary data


0003-QML-UI-add-Subsurface-mobile-to-top-of-app.patch
Description: Binary data


0004-QML-UI-add-style-to-the-menu-button.patch
Description: Binary data

/Jocke

___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Unable to download logs from Petrel3 w/ android app

[Attilla de Groot via subsurface]

Hi,

This morning I made my first ccr dive (of course it was horrible, I need to 
learn to dive again...) .


I have a Petrel3 with it, but I'm unable to download the dive log to the 
android app (I'll try later with my laptop). It connects, the computer says 
it's sending, but subsurface claims there are now new logs. The shearwater 
app itself is able to download them though.


I've put the logs here: 
https://gist.github.com/packetninja/3ac8d18b9feb56edbde4e7414815a7b9


I know it's a new model so if there's anything else I can do, let me know.


-- Attilla
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: [PATCH] start making the android app more mobile friendly.

[Dirk Hohndel]

It's hard to quote these patches as they are not attached as text :-(

And I'd love to be able to actually discuss them

On Sun, Jul 26, 2015 at 02:13:34PM +0200, Joakim Bygdell wrote:
> 0001: Moves the buttons to a popup menu accessible from a single button, as 
> they don’t fit on the screen of a phone.

This is certainly a way to do this but I don't think it's THE way to do
it. No one is currently really "designing" the mobile app as we are all
learning what we are doing.
And of course as Devide has long since explained, emails are really a bad
way to discuss design work.

I realize that many apps have menues and that Android even has this design
pattern to some extend, but if I look at apps that I find easy to use then
the menu pattern is used for things that you usually don't need. And at
least the "Load dives" button in the current implementation is something
you need frequently. Of course one could make the argument that once the
preferences are set you should simply show the dives when you open the app
and then this change would make more sense.

Hmm, I think discussing your change and telling you why it's wrong
convinced me that maybe it isn't wrong after all :-)

> 0002: Change the background to the same blue as in the icon.
> 0003: Add the name to the top row of the UI.

Nice. We do lose that top row as we show details, but I guess "one step at
a time" is the right answer here.

> 0004: Style the menu button to fit the theme.

Thanks Jocke, this is really cool. I'll talk to Grace about this but I
think I might take these changes.

/D
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: [PATCH] start making the android app more mobile friendly.

[Grace Karanja]

On Sun, Jul 26, 2015 at 3:13 PM, Joakim Bygdell  wrote:

> 0001: Moves the buttons to a popup menu accessible from a single button,
> as they don’t fit on the screen of a phone.
> 0002: Change the background to the same blue as in the icon.
> 0003: Add the name to the top row of the UI.
> 0004: Style the menu button to fit the theme.
>


Thanks for these, it looks much better on mobile :)

Dirk, I think you can add these to mater, then we can build up on them.
--
Grace K
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: [PATCH] start making the android app more mobile friendly.

[Dirk Hohndel]

On Sun, Jul 26, 2015 at 04:57:34PM +0300, Grace Karanja wrote:
> On Sun, Jul 26, 2015 at 3:13 PM, Joakim Bygdell  wrote:
> 
> > 0001: Moves the buttons to a popup menu accessible from a single button,
> > as they don’t fit on the screen of a phone.
> > 0002: Change the background to the same blue as in the icon.
> > 0003: Add the name to the top row of the UI.
> > 0004: Style the menu button to fit the theme.
> >
> 
> 
> Thanks for these, it looks much better on mobile :)
> 
> Dirk, I think you can add these to mater, then we can build up on them.

They have been added to master and pushed.

Thanks

/D
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: [PATCH] start making the android app more mobile friendly.

[Joakim Bygdell]

> On 26 Jul 2015, at 15:39, Dirk Hohndel  wrote:
> 
> It's hard to quote these patches as they are not attached as text :-(
> 
> And I'd love to be able to actually discuss them
> 
> On Sun, Jul 26, 2015 at 02:13:34PM +0200, Joakim Bygdell wrote:
>> 0001: Moves the buttons to a popup menu accessible from a single button, as 
>> they don’t fit on the screen of a phone.
> 
> This is certainly a way to do this but I don't think it's THE way to do
> it. No one is currently really "designing" the mobile app as we are all
> learning what we are doing.
> And of course as Devide has long since explained, emails are really a bad
> way to discuss design work.
> 
> I realize that many apps have menues and that Android even has this design
> pattern to some extend, but if I look at apps that I find easy to use then
> the menu pattern is used for things that you usually don't need. And at
> least the "Load dives" button in the current implementation is something
> you need frequently. Of course one could make the argument that once the
> preferences are set you should simply show the dives when you open the app
> and then this change would make more sense.
> 
> Hmm, I think discussing your change and telling you why it's wrong
> convinced me that maybe it isn't wrong after all :-)
> 

At least it is a start of making the app fit a screen that is 4-6 inches 
diagonal.
And YES the app should load the divest automatically once you have entered the 
credentials.
Also I think we need to implement that swiping down from the top loads the 
dices or something similar.


/Jocke

___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

RE: [PATCH] start making the android app more mobile friendly.

[Steve]

Dirk Hohndel dirk at hohndel.org
Sun Jul 26 07:14:19 PDT 2015

-Original Message-
On Sun, Jul 26, 2015 at 04:57:34PM +0300, Grace Karanja wrote:
> On Sun, Jul 26, 2015 at 3:13 PM, Joakim Bygdell  
> wrote:
> 
> > 0001: Moves the buttons to a popup menu accessible from a single button,
> > as they don’t fit on the screen of a phone.
> > 0002: Change the background to the same blue as in the icon.
> > 0003: Add the name to the top row of the UI.
> > 0004: Style the menu button to fit the theme.
> >
> 
> 
> Thanks for these, it looks much better on mobile :)
> 
> Dirk, I think you can add these to mater, then we can build up on them.

They have been added to master and pushed.

Thanks

/D


Just FYI on a Samsung S4 4.3 I cannot get to the menu by pressing the usual 
menu key (or any other way I can think of).

___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

RE: [PATCH] start making the android app more mobile friendly.

[Rick Walsh]

Hi Steve,

On 27 Jul 2015 2:56 pm, "Steve"  wrote:
>
>
> Dirk Hohndel dirk at hohndel.org
> Sun Jul 26 07:14:19 PDT 2015
>
> -Original Message-
> On Sun, Jul 26, 2015 at 04:57:34PM +0300, Grace Karanja wrote:
> > On Sun, Jul 26, 2015 at 3:13 PM, Joakim Bygdell 
wrote:
> >
> > > 0001: Moves the buttons to a popup menu accessible from a single
button,
> > > as they don’t fit on the screen of a phone.
> > > 0002: Change the background to the same blue as in the icon.
> > > 0003: Add the name to the top row of the UI.
> > > 0004: Style the menu button to fit the theme.
> > >
> >
> >
> > Thanks for these, it looks much better on mobile :)
> >
> > Dirk, I think you can add these to mater, then we can build up on them.
>
> They have been added to master and pushed.
>
> Thanks
>
> /D
>
>
> Just FYI on a Samsung S4 4.3 I cannot get to the menu by pressing the
usual menu key (or any other way I can think of).

It works on my Samsung Galaxy S6. The menu button is three dots on the top
right of the screen.

Cheers,

Rick
>
> ___
> subsurface mailing list
> subsurface@subsurface-divelog.org
> http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
>
> ___
> subsurface mailing list
> subsurface@subsurface-divelog.org
> http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: [PATCH] start making the android app more mobile friendly.

[Benjamin]

Good morning.
Where can one download a version of the "nightly" apk for testing?

Benjamin

On Mon, 27 Jul 2015 07:56 Steve  wrote:

>
> Dirk Hohndel dirk at hohndel.org
> Sun Jul 26 07:14:19 PDT 2015
>
> -Original Message-
> On Sun, Jul 26, 2015 at 04:57:34PM +0300, Grace Karanja wrote:
> > On Sun, Jul 26, 2015 at 3:13 PM, Joakim Bygdell 
> wrote:
> >
> > > 0001: Moves the buttons to a popup menu accessible from a single
> button,
> > > as they don’t fit on the screen of a phone.
> > > 0002: Change the background to the same blue as in the icon.
> > > 0003: Add the name to the top row of the UI.
> > > 0004: Style the menu button to fit the theme.
> > >
> >
> >
> > Thanks for these, it looks much better on mobile :)
> >
> > Dirk, I think you can add these to mater, then we can build up on them.
>
> They have been added to master and pushed.
>
> Thanks
>
> /D
>
>
> Just FYI on a Samsung S4 4.3 I cannot get to the menu by pressing the
> usual menu key (or any other way I can think of).
>
> ___
> subsurface mailing list
> subsurface@subsurface-divelog.org
> http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
>
> ___
> subsurface mailing list
> subsurface@subsurface-divelog.org
> http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
>
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: [PATCH] start making the android app more mobile friendly.

[Miika Turkia]

http://subsurface-divelog.org/downloads/daily/

miika

On Mon, Jul 27, 2015 at 8:14 AM, Benjamin  wrote:
> Good morning.
> Where can one download a version of the "nightly" apk for testing?
>
> Benjamin
>
>
> On Mon, 27 Jul 2015 07:56 Steve  wrote:
>>
>>
>> Dirk Hohndel dirk at hohndel.org
>> Sun Jul 26 07:14:19 PDT 2015
>>
>> -Original Message-
>> On Sun, Jul 26, 2015 at 04:57:34PM +0300, Grace Karanja wrote:
>> > On Sun, Jul 26, 2015 at 3:13 PM, Joakim Bygdell 
>> > wrote:
>> >
>> > > 0001: Moves the buttons to a popup menu accessible from a single
>> > > button,
>> > > as they don’t fit on the screen of a phone.
>> > > 0002: Change the background to the same blue as in the icon.
>> > > 0003: Add the name to the top row of the UI.
>> > > 0004: Style the menu button to fit the theme.
>> > >
>> >
>> >
>> > Thanks for these, it looks much better on mobile :)
>> >
>> > Dirk, I think you can add these to mater, then we can build up on them.
>>
>> They have been added to master and pushed.
>>
>> Thanks
>>
>> /D
>>
>>
>> Just FYI on a Samsung S4 4.3 I cannot get to the menu by pressing the
>> usual menu key (or any other way I can think of).
>>
>> ___
>> subsurface mailing list
>> subsurface@subsurface-divelog.org
>> http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
>>
>> ___
>> subsurface mailing list
>> subsurface@subsurface-divelog.org
>> http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
>
>
> ___
> subsurface mailing list
> subsurface@subsurface-divelog.org
> http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
>
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: [PATCH] start making the android app more mobile friendly.

[Benjamin]

On 27 Jul 2015 08:15, "Miika Turkia"  wrote:
>
> http://subsurface-divelog.org/downloads/daily/
>
> miika
>
> On Mon, Jul 27, 2015 at 8:14 AM, Benjamin  wrote:
> > Good morning.
> > Where can one download a version of the "nightly" apk for testing?
> >
> > Benjamin

Thank you.
And sorry for the top post :(

Benjamin
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: [PATCH] start making the android app more mobile friendly.

[Joakim Bygdell]

> On 27 Jul 2015, at 8:20, Rick Walsh  wrote:
> 
> 
> On 27 Jul 2015 3:42 pm, "Steve"  > wrote:
> >
> > > Just FYI on a Samsung S4 4.3 I cannot get to the menu by pressing the 
> > > usual menu key (or any other way I can think of).
> >
> > It works on my Samsung Galaxy S6. The menu button is three dots on the top 
> > right of the screen.
> >
> > Cheers,
> >
> > Rick
> >
> >  
> >
> > I don’t see dots but pressing the top right corner it works.
> 
The dots are a vertical ellipsis and generated via unicode character. So it 
might be that your phone have some problems with that.
I can build a version for you Steve that a have a border around the button, 
then we can see more easily where the problem is.

> That's interesting. I believe it is supposed to look similar on all devices. 
> Perhaps it's to do with a different screen resolution? I've attached a 
> screenshot of what it looks like on my phone, which I assume is how it's 
> intended to look.
> 
There is nothing that specifies the width of the top row so it should be 
resolution independent.
> >
> > When I read menu I was trying the capacitive left button on the bottom of 
> > the phone.
> 
> The new Samsungs don't have that button.  And I miss it.  Predictably, my s4 
> died not long after it was past its warranty period.
> 
> R
> ___
> subsurface mailing list
> subsurface@subsurface-divelog.org
> http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

/Jocke

___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: [PATCH] start making the android app more mobile friendly.

[Joakim Bygdell]

> On 27 Jul 2015, at 9:48, Steve  wrote:
> 
> I can see the white square outline in the top right corner in this version.
> 
> Regards,
> Steve

Then our phone have problems with unicode characters.

/Jocke

___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: [PATCH] start making the android app more mobile friendly.

[Grace Karanja]

On Mon, Jul 27, 2015 at 7:56 AM, Steve 
wrote:

>
> Just FYI on a Samsung S4 4.3 I cannot get to the menu by pressing the
> usual menu key (or any other way I can think of).
>
>
Hi,
I will get a device with a menu key and test/implement this. Ideally
pressing the menu key should bring up the menu.


-- 
--
Grace K
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

RE: [PATCH] start making the android app more mobile friendly.

[Steve]

I also see the profile sometimes cut off at the end.

 

I wonder if it is the scaling button (on the desktop version). I tried to set 
it to always be on but every time it turns itself off when subsurface is 
restarted. So default to not scale the profile.

 

Steve

 

From: subsurface [mailto:subsurface-boun...@subsurface-divelog.org] On Behalf 
Of David Tillotson
Sent: Tuesday, 28 July 2015 6:17 AM
To: Subsurface Mailing List 
Subject: Re: [PATCH] start making the android app more mobile friendly.

 

On 26 July 2015 15:14:19 BST, Dirk Hohndel mailto:d...@hohndel.org> > wrote:

On Sun, Jul 26, 2015 at 04:57:34PM +0300, Grace Karanja wrote:

 On Sun, Jul 26, 2015 at 3:13 PM, Joakim Bygdell mailto:j.bygd...@gmail.com> > wrote:
 

 0001: Moves the buttons to a popup menu accessible from a single button,
 as they don’t fit on the screen of a phone.
 0002: Change the background to the same blue as in the icon.
 0003: Add the name to the top row of the UI.
 0004: Style the menu button to fit the theme.


 
 
 Thanks for these, it looks much better on mobile :)
 
 Dirk, I think you can add these to mater, then we can build up on them.


They have been added to master and pushed.

Thanks

/D


  _  


subsurface mailing list
subsurface@subsurface-divelog.org <mailto:subsurface@subsurface-divelog.org> 
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface


I haven't been following the Android build status until recently, and I have to 
say I am very impressed. On my Note 4 there is an odd issue with the graph area 
being cut off around half way across (screenshot attached).
As yet I haven't managed to connect to the Reefnet Sensus Pro, but I suspect 
the USB to serial adapter is more of an issue than the app.
-- 
David Tillotson

___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

interesting Kirigami / Qt 5.6 interaction [was Re: Android app -923]

[Dirk Hohndel]

Marco, Sebastian,

If you have a moment, please try the latest -923 version of 
Subsurface-mobile.apk,
which was built using Qt 5.6.0 RC. Using one of the test accounts, load a dive 
list, 
select a dive and switch to landscape mode.

Observe this crazy effect where only the left half of the screen is used, the 
right side
stays empty.

You can reproduce something very similar on a desktop as well where a third,
empty page is created to the right of the dive details view. I hacked around 
the Qt 5.6
crash that Marco ran into today while working on the notification issue, so you 
should
now be able to use Subsurface-mobile latest master with Qt 5.6.0 RC without a 
problem.

I tried to create a screen video to demonstrate this but clearly my skill with 
the 
Android screen recording tools is insufficient, but this is so easy to 
reproduced (I tried
on three different devices), I hope you can just check this for yourself.

Any idea how to fix this? Is this some weird rounding thing where the math goes
wrong and we create an extra page for some odd reason?

Thanks for looking into this

/D

> On Mar 3, 2016, at 3:22 PM, Dirk Hohndel  wrote:
> 
> This is back to using Qt 5.6.0.
> In order to avoid the crashes we've been seeing with that I now switched
> the grid layout on the dive details page to be fixed column width (so
> we're setting both the preferred and the maximum width to the same value).
> 
> The notification for cloud access seems to work in all the scenarios that
> I could think of testing.
> 
> The list of known outstanding bugs is getting really small.
> 
> Sebas, now that we are on Qt 5.6... do you remember what you and I tested
> a couple of months ago with getting the correct keyboard geometry from Qt?
> I know that worked with 5.6... so maybe you could create a Kirigami patch
> to use that data so the users don't need to close the keyboard to access
> the bottom part of a page?
> 
> Other than that... localization, but I'm OK with having the first release
> just in English, to be honest. What else is broken?
> 
> I'll give it a day (since the Europeans most likely are asleep by now) and
> then maybe make another beta tomorrow. And then maybe we can work our way
> towards a first release next week?
> 
> /D
> ___
> subsurface mailing list
> subsurface@subsurface-divelog.org
> http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Unable to download logs from Petrel3 w/ android app

[Jef Driesen via subsurface]

On 4/09/2022 13:34, Attilla de Groot via subsurface wrote:
This morning I made my first ccr dive (of course it was horrible, I need to 
learn to dive again...) .


I have a Petrel3 with it, but I'm unable to download the dive log to the android 
app (I'll try later with my laptop). It connects, the computer says it's 
sending, but subsurface claims there are now new logs. The shearwater app itself 
is able to download them though.


I've put the logs here: 
https://gist.github.com/packetninja/3ac8d18b9feb56edbde4e7414815a7b9 


I know it's a new model so if there's anything else I can do, let me know.


According to the logs, there were two dives downloaded:

  2022-07-29 21:14:40
  2017-01-01 01:31:37

That's clearly not a dive done "this morning", but both dives were CCR dives 
according to the dive mode. Is the clock of your dive computer set correctly?


I don't see any other dives present in the manifest (all zeros).

Jef
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Unable to download logs from Petrel3 w/ android app

[Jef Driesen via subsurface]

On 5/09/2022 12:46, Attilla de Groot wrote:
On 5 Sep 2022, at 12:19, Jef Driesen <mailto:j...@libdivecomputer.org>> wrote:

According to the logs, there were two dives downloaded:

 2022-07-29 21:14:40
 2017-01-01 01:31:37

That's clearly not a dive done "this morning", but both dives were CCR dives 
according to the dive mode. Is the clock of your dive computer set correctly?


I don't see any other dives present in the manifest (all zeros).


Those two were downloaded from the Nerd2 that indeed had the date/time 
incorrectly set. Downloading from the Nerd2 worked without problems, the first 
was the factory test and the second the  actual dive from 2022-09-04, but with 
the wrong date.


Okay, that log had nothing to do with the problem you are reporting. That's just 
confusing.


Before that, I tried at least 5 times to download the dives from the Petrel3. 
Dirk reached out directly and suggested I try the QT6 build on my laptop with 
the Petrel3. That made BT work, but gave the same problem as the Android app 
(“No new dives downloaded from dive computer”). Despite starting it in verbose 
mode, the only thing in the red bar says: “Dive 1: Error parsing the 
header”.Tried multiple times in various ways (with/without force, removing the 
imported dive etc.), but that didn’t change the result.


Try again with the "Save libdivecomputer logfile" checkbox enabled, and email me 
the log file.


Jef
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Unable to download logs from Petrel3 w/ android app

[Jef Driesen via subsurface]

On 5/09/2022 17:25, Attilla de Groot wrote:

I looked at the dive profile and the xml, but I don’t see anything that would
explain this. I was just diving with 100% o2 and AIR as diluent. I did have a
transmitter to my bailout stage that also had AIR. Could this be related?

I have downloaded the log through the shearwater (android) app and exported
it to Subsurface. A bit of a long way around, but in the end it worked. I
have attached those outputs, perhaps that helps in any way?


That shearwater xml file is interesting because it also contains a large amount 
of gas mixes, and many of those contain invalid values (e.g. 02 percentages 
larger than 100%).


For example the first sample contains:

1.29
0

That's a mix containing 129% 02, which of course doesn't make any sense. When 
importing the dive into shearwater cloud desktop, I also get those many gas 
switches and the invalid values. See the attached screenshot.


Except for those fractionO2 values, the rest of the data looks normal. So at 
first sight the problem appears to be in the raw data, and not the parsing. 
Maybe a bug in the Petrel firmware? I'll report the problem to shearwater.


The UDDF export doesn't seem to contain any gas mix info at all, and when 
importing the shearwater xml into subsurface, the gas mix info seems to be 
ignored too. So that's probably why your workaround is working.


Jef___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Unable to download logs from Petrel3 w/ android app

[Attilla de Groot via subsurface]

> On 7 Sep 2022, at 10:32, Jef Driesen  wrote:
> 
> On 5/09/2022 17:25, Attilla de Groot wrote:
>> I looked at the dive profile and the xml, but I don’t see anything that would
>> explain this. I was just diving with 100% o2 and AIR as diluent. I did have a
>> transmitter to my bailout stage that also had AIR. Could this be related?
>> I have downloaded the log through the shearwater (android) app and exported
>> it to Subsurface. A bit of a long way around, but in the end it worked. I
>> have attached those outputs, perhaps that helps in any way?
> 
> That shearwater xml file is interesting because it also contains a large 
> amount of gas mixes, and many of those contain invalid values (e.g. 02 
> percentages larger than 100%).
> 
> For example the first sample contains:
> 
>1.29
>0
> 
> That's a mix containing 129% 02, which of course doesn't make any sense. When 
> importing the dive into shearwater cloud desktop, I also get those many gas 
> switches and the invalid values. See the attached screenshot.
> 
> Except for those fractionO2 values, the rest of the data looks normal. So at 
> first sight the problem appears to be in the raw data, and not the parsing. 
> Maybe a bug in the Petrel firmware? I'll report the problem to shearwater.
> 
> The UDDF export doesn't seem to contain any gas mix info at all, and when 
> importing the shearwater xml into subsurface, the gas mix info seems to be 
> ignored too. So that's probably why your workaround is working.

Thank you for looking into this, much appreciated. I’m curious how shearwater 
will respond.

I have planned another CCR dive tomorrow. I’ll provide the same data again for 
that dive.


— Attilla
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Unable to download logs from Petrel3 w/ android app

[Jef Driesen via subsurface]

On 18/12/2022 20:22, Attilla de Groot wrote:

Shearwater has solved this issue in their latest update (v93). It now looks 
nicely in their own app as well and I’m able to download the logs directly into 
subsurface.


Fixed as in new dives are now recorded correctly? Or is the data also fixed for 
your previously recorded dives? I assume only for the new dives?



One question on my specific CCR logs. The XCCR has integrated pressure sensors 
for O2 and DIL. These are available on the Petrel3 (not my Nerd2 btw) and also 
displayed in Shearwater cloud after importing the dive:

Unfortunately I don’t see these in Subsurface. Not sure if it would be useful, 
but I would like to have the data. The data itself doesn’t seem to be exported 
in Shearwaters own export format or UDDF (see attached). Is this a setting I 
would need to change to get it in Subsurface or is this simply not supported?


There are indeed a few differences for XCCR, which I didn't investigate further 
because I didn't have such data. I'll need to have a look at the raw data for 
that. Can you enable the "Save libdivecomputer logfile", do a full download 
(with "Force download of all dives" enabled) and send me the log file?


Jef
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface