RE: who has BLE dive computers - which one, which OSs can you test
Shearwater Petrel 2 dual stack Heinrich Weikamp OSTC3+ dual stack Windows 10 Fedora Linux Android Steve Hi there, I asked almost the same question before, but only a few people answered... I'm trying to figure out how much coverage we have for testing BLE support, but at this point I can't really tell how many of us have access to such devices (and which OSs they might be testing on). So, could you please respond and tell me - which BLE dive computer do you have access to (So far only support Suunto EON Steel, Heinrich Weikamp OSTC 4, Shearwater Perdix AI (and dual stack Perdix / Petrel 2), and Scubapro G2 -- if you have others, I'd love to know as well) - which OSs can you test on I'll start: Suunto EON Steel Shearwater Perdix AI Shearwater Petrel 2 dual stack Mac Linux (only Fedora on a physical machine, BLE doesn't work in a VM) Windows (currently an ancient netbook with BLE dongle) Android iOS Thanks /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: Slow switching between dives?
On 29 September 2017 at 03:05, Linus Torvaldswrote: > Ho humm. I haven't actually bisected this or anything, but I'm hoping > somebody else noticed and might have picked up on when this started.. > > I've got a fast CPU, but switching dives isn't "instant". You can > particularly tell when just scrolling down the dive list using the > cursor keys. It's not *slow*, but it sure isn't fast. > > We used to have this situation where the deco processing took up a lot > of time, but that doesn't seem to be it. Yes, "add_segment()" is > fairly high in the profiles at 11% of CPU time, and "factor()" is > another 4% or so, but that's pretty much it. Most of the time seems to > be GUI costs. > > The top entry in a profile of me scrolling down the list is > > 12.55% qt_qimageScaleAARGBA_down_xy_sse4 > > but there's some truetype code at 3% and a lot of libQt5Gui stuff in > the ~1% range. > > I *thought* we used to update the dive profile asynchronously so that > you could step down the dive log without waiting for the profile to > render all the time. Has that code bit-rotted perhaps? > > Or is it just me? > i'm on a relatively slow machine and it has been always kind of slow to switch between dives, so i can't really tell the difference. just did a quick profiling myself to see if it's the map widget is responsible and i do not observe heavy loads in QtLocation, QtPositioning, QtQml. might still be it, but my guess is that it's unrelated to the new map. lubomir -- ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Slow switching between dives?
Ho humm. I haven't actually bisected this or anything, but I'm hoping somebody else noticed and might have picked up on when this started.. I've got a fast CPU, but switching dives isn't "instant". You can particularly tell when just scrolling down the dive list using the cursor keys. It's not *slow*, but it sure isn't fast. We used to have this situation where the deco processing took up a lot of time, but that doesn't seem to be it. Yes, "add_segment()" is fairly high in the profiles at 11% of CPU time, and "factor()" is another 4% or so, but that's pretty much it. Most of the time seems to be GUI costs. The top entry in a profile of me scrolling down the list is 12.55% qt_qimageScaleAARGBA_down_xy_sse4 but there's some truetype code at 3% and a lot of libQt5Gui stuff in the ~1% range. I *thought* we used to update the dive profile asynchronously so that you could step down the dive log without waiting for the profile to render all the time. Has that code bit-rotted perhaps? Or is it just me? Linus ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: subsurface Digest, Vol 70, Issue 57
Hi all, To the question who bas a ble dive computer, me. A perdix ai. I can test windows 10 ans ubuntu 17.04 and Android 8 ans 7.1.2. Bye Eric Message original De : subsurface-requ...@subsurface-divelog.org Envoyé : Thursday, September 28, 2017 09:00 PM À : subsurface@subsurface-divelog.org Sujet : subsurface Digest, Vol 70, Issue 57 >Send subsurface mailing list submissions to > subsurface@subsurface-divelog.org > >To subscribe or unsubscribe via the World Wide Web, visit > http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface > >or, via email, send a message with subject or body 'help' to > subsurface-requ...@subsurface-divelog.org > >You can reach the person managing the list at > subsurface-ow...@subsurface-divelog.org > >When replying, please edit your Subject line so it is more specific >than "Re: Contents of subsurface digest..." > > >Today's Topics: > > 1. Re: thinking about 4.7 (Tomaz Canabrava) > 2. Re: who has BLE dive computers - which one, which OSs can you > test (Seppo Takalo) > > >-- > >Message: 1 >Date: Thu, 28 Sep 2017 10:43:40 +0200 >From: Tomaz Canabrava <tcanabr...@kde.org> >To: Dirk Hohndel <d...@hohndel.org> >Cc: Federico Masias <f...@masias.net>, Subsurface Mailing List > <subsurface@subsurface-divelog.org> >Subject: Re: thinking about 4.7 >Message-ID: > <cack01_yc1ifma1u1bkm5mzo9a8epqbrv5ox61-bk8a1shbg...@mail.gmail.com> >Content-Type: text/plain; charset="utf-8" > >looking today. > >On Wed, Sep 27, 2017 at 4:54 PM, Dirk Hohndel <d...@hohndel.org> wrote: > >> On Wed, Sep 27, 2017 at 01:50:32PM +0200, Tomaz Canabrava wrote: >> > On Wed, Sep 27, 2017 at 5:41 AM, Dirk Hohndel <d...@hohndel.org> wrote: >> > >> > > On Tue, Sep 26, 2017 at 11:21:59PM -0400, Federico Masias wrote: >> > > > > >> > > > > >> > > > > Yes it is. Please do. >> > > > > >> > > > >> > > > Done. >> > > >> > > Thanks, already merged >> > > >> > > > > > Facebook upload mostly works, but Subsurface asks for an album >> name >> > > to >> > > > > place the photo into an album... but Facebook simply posts it to an >> > > album >> > > > > called "Subsurface Photos" -- no mention of the user defined album >> > > > > anywhere. I'd also caution against using the verbiage of "profile >> > > picture" >> > > > > in the instructions when referring to the dive profile graph, as >> that >> > > > > phrase means something else completely to Facebook users. >> > > > > >> > > > > Both great points. Can you fix this in the code? Otherwise, please >> > > raise >> > > > > an issue on Github. >> > > > > These are both easy to address >> > > > > >> > > > > >> > > > I was able to change the string, but I've noticed a few more things >> about >> > > > the parameters that are passed to Facebook, so I'll raise a Github >> issue >> > > > about that shortly, but the short version is that I'm not sure if >> we're >> > > > passing the wrong info to the FB API, or it's being ignored -- both >> for >> > > the >> > > > album name and privacy settings. I don't have time tonight to >> > > investigate, >> > > > and I'm sure someone around here is much better at it than I -- but >> if >> > > it's >> > > > not fixed by someone else, I'll try and follow up on it when I do >> have a >> > > > bit more time. >> > > >> > > Tomaz recently updated our code to the latest API version. Did you test >> > > with the latest test version or with the last release version? If the >> > > former, let's make sure you tag @tcanabrava in the issue so he can look >> > > into this to see if maybe something got mixed up with the change to the >> > > newer API. >> > > >> > >> > The latest api version was just a number change, no actuall api methods >> > where modified. >> >> Did you have a chance to take a look at the bug report? >> >> https://github.com/Subsurface-divelog/subsurface/issues/612 >> >> Thanks >> >> /D >> >-
Re: who has BLE dive computers - which one, which OSs can you test
On 19 September 2017 at 17:45, Dirk Hohndelwrote: > > So, could you please respond and tell me > > - which BLE dive computer do you have access to > > > - which OSs can you test on > Shearwater Perdix AI Mac OS X 10.11.6, Macbook Pro 2010, using separate BLE dongle that came with the Perdix. Qt 5.9.1 Subsurface v4.6.4-848-g2a29d4a4 Test: Initial download always fails (as already reported here), I need to first scan and then select the device. Succesfully downloads 5 dives, then Perdix reports "LOG ERROR: Timeout" and Subsurface shows "Error\n Dive data import error" After re-starting Bluetooth from Perdix and clicking "Retry dowload" from Subsurface seems to continue and download more dives until finally popping the "Error\nDive data import error" message. This time no error messages on Perdix and all dives seems to be successfully imported, regardless of the error message. -- /--\ | O O | Seppo Takalo | ^ | +358503812218 | \__/ | seppo.tak...@iki.fi \--/- ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: thinking about 4.7
looking today. On Wed, Sep 27, 2017 at 4:54 PM, Dirk Hohndelwrote: > On Wed, Sep 27, 2017 at 01:50:32PM +0200, Tomaz Canabrava wrote: > > On Wed, Sep 27, 2017 at 5:41 AM, Dirk Hohndel wrote: > > > > > On Tue, Sep 26, 2017 at 11:21:59PM -0400, Federico Masias wrote: > > > > > > > > > > > > > > > Yes it is. Please do. > > > > > > > > > > > > > Done. > > > > > > Thanks, already merged > > > > > > > > > Facebook upload mostly works, but Subsurface asks for an album > name > > > to > > > > > place the photo into an album... but Facebook simply posts it to an > > > album > > > > > called "Subsurface Photos" -- no mention of the user defined album > > > > > anywhere. I'd also caution against using the verbiage of "profile > > > picture" > > > > > in the instructions when referring to the dive profile graph, as > that > > > > > phrase means something else completely to Facebook users. > > > > > > > > > > Both great points. Can you fix this in the code? Otherwise, please > > > raise > > > > > an issue on Github. > > > > > These are both easy to address > > > > > > > > > > > > > > I was able to change the string, but I've noticed a few more things > about > > > > the parameters that are passed to Facebook, so I'll raise a Github > issue > > > > about that shortly, but the short version is that I'm not sure if > we're > > > > passing the wrong info to the FB API, or it's being ignored -- both > for > > > the > > > > album name and privacy settings. I don't have time tonight to > > > investigate, > > > > and I'm sure someone around here is much better at it than I -- but > if > > > it's > > > > not fixed by someone else, I'll try and follow up on it when I do > have a > > > > bit more time. > > > > > > Tomaz recently updated our code to the latest API version. Did you test > > > with the latest test version or with the last release version? If the > > > former, let's make sure you tag @tcanabrava in the issue so he can look > > > into this to see if maybe something got mixed up with the change to the > > > newer API. > > > > > > > The latest api version was just a number change, no actuall api methods > > where modified. > > Did you have a chance to take a look at the bug report? > > https://github.com/Subsurface-divelog/subsurface/issues/612 > > Thanks > > /D > ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface