Re: Subsurface-mobile support request / Lost Logs when synced to cloud
I'm glad I was able to help All the best /D On October 16, 2023 10:18:00 PM EDT, Callie K wrote: >Hi Dirk, > >Wow! You are amazing… Thank you so much. > >I am sorry I have inconvenienced you with this problem, and express my deepest >appreciation and gratitude for helping me. That is extremely kind and generous >of you. > >Thank you for telling me how to avoid this issue again. > >I would like to make a contribution or a donation if there is a PayPal or >Venmo name, or a credit card app that I could contribute to. Please let me >know. > >Thank you, and all your associates for your devotion, care and great work. > >Respectfully, >Callie > > > >On Oct 15, 2023, at 10:47 PM, Dirk Hohndel wrote: > > Hi Callie, > >It took about a solid hour of work, but I believe I have restored all of the >deleted dives in your cloud account. > >Please refresh (ideally on all of your devices/computers) the cloud storage >account to make sure everything is where you want it to be. >I may have lost a dive site or two in the process (if I did, then it's for >dives on Oct 7 and 8), but I think everything else should be back to normal. > >And to reiterate what I wrote before, to ensure that you don't get into this >situation again, please ensure that you ALWAYS manually sync with the cloud >storage before editing dives or downloading dives from a dive computer. > >Sorry for the inconvenience. > >/D > >On Oct 15, 2023, at 17:23, Callie K wrote: > >Hello Dirk, > >Thank you for your email. > >First of all, I would like to thank you for the product/service and now >understand this is a hobby for a bunch of people. A great hobby! > >I’m sorry if my message came across as if there is a misunderstanding as to >what is happening. There was no anger outbursts directed towards the >developers, nor anger channeled in any direction whatsoever. Frustration with >the failure or under development, of what I now understand happened, yes. I >always recognize that there are bugs, issues, and unknowns that surface >continually and throughout our evolution of IT advancement. I am a solution >driven individual who understands things happen and always try to find >solutions, and then preventative measures. May be a better way for me to use >Subsurface. > >I think what I take from this, and your dramatic email, is that, a couple >websites so highly recommend your product/service without sharing, or me >recognizing, it is not a business level system. Also, lost data occurrences >frequently do happen with users, and there may be some under development >issues, and that’s okay. After this happened to me, I did Google everything >looking for a solution and found that it has a pattern that occurs more >frequently. > >I relied on it perhaps more than I was aware that I should have. And I have no >problem using a paid service, because, this information is rather important in >its’ nature for what I am using it for. > >As I said earlier here, I did Google the issue. I do have a Google account, >and in excellent standing. I am an upstanding citizen. My reference of “not >allow me in” was due to the fact that I was “not a member“ of the group. I had >a difficult time and ultimately, not able to learn how to either request, or >add this group to my Google account, for access. When I followed the links to >all the similar problems I found, they led to the Google Account. Again, it >allowed me to only read maybe the first few sentences or post. It would not >allow me to see the additional comments, and understand it further. Either >from my lack of experience with the Subsurface set up, or not being able to >identify how to or, what the name of the group was, to add to my Google >account. > >I was unaware that I was using a developer emailing list. I came across an >email that appeared to be a support email. I am not interested in having >developer access. > >I’m sorry if my description came across garbled and confusing. I opened up >Subsurface app on my computer to enter some logs. I noticed one of the logs >and edited the name. If I recall correctly, I saved it to the cloud, and then >I noticed I was missing a few dive logs. So then I entered a “test dive“ to >see if there was a server updating concern. Upon entering it, I saved it to >the cloud on my computer, and then it deleted all the other logs, and had just >that one “test log”. As I said, in the other email, I know for sure I did not >delete any dive logs. > >I believe I closed out the computer and opened my iPhone, and saw that the >three or four were still missing the few dives, but had all the others there. >So I synced it to the cloud, and then it deleted the rest of them, and only >left me with the “test’ dive”. > >Yes, I would appreciate your help in restoring them and am giving explicit >permission to help me in any way that you can. I understand this is a hobby, >and would be okay if I had to just write it off and re-create it again, or >even
Re: Subsurface-mobile support request / Lost Logs when synced to cloud
Hi Dirk, Wow! You are amazing… Thank you so much. I am sorry I have inconvenienced you with this problem, and express my deepest appreciation and gratitude for helping me. That is extremely kind and generous of you. Thank you for telling me how to avoid this issue again. I would like to make a contribution or a donation if there is a PayPal or Venmo name, or a credit card app that I could contribute to. Please let me know. Thank you, and all your associates for your devotion, care and great work. Respectfully, Callie On Oct 15, 2023, at 10:47 PM, Dirk Hohndel wrote: Hi Callie, It took about a solid hour of work, but I believe I have restored all of the deleted dives in your cloud account. Please refresh (ideally on all of your devices/computers) the cloud storage account to make sure everything is where you want it to be. I may have lost a dive site or two in the process (if I did, then it's for dives on Oct 7 and 8), but I think everything else should be back to normal. And to reiterate what I wrote before, to ensure that you don't get into this situation again, please ensure that you ALWAYS manually sync with the cloud storage before editing dives or downloading dives from a dive computer. Sorry for the inconvenience. /D On Oct 15, 2023, at 17:23, Callie K wrote: Hello Dirk, Thank you for your email. First of all, I would like to thank you for the product/service and now understand this is a hobby for a bunch of people. A great hobby! I’m sorry if my message came across as if there is a misunderstanding as to what is happening. There was no anger outbursts directed towards the developers, nor anger channeled in any direction whatsoever. Frustration with the failure or under development, of what I now understand happened, yes. I always recognize that there are bugs, issues, and unknowns that surface continually and throughout our evolution of IT advancement. I am a solution driven individual who understands things happen and always try to find solutions, and then preventative measures. May be a better way for me to use Subsurface. I think what I take from this, and your dramatic email, is that, a couple websites so highly recommend your product/service without sharing, or me recognizing, it is not a business level system. Also, lost data occurrences frequently do happen with users, and there may be some under development issues, and that’s okay. After this happened to me, I did Google everything looking for a solution and found that it has a pattern that occurs more frequently. I relied on it perhaps more than I was aware that I should have. And I have no problem using a paid service, because, this information is rather important in its’ nature for what I am using it for. As I said earlier here, I did Google the issue. I do have a Google account, and in excellent standing. I am an upstanding citizen. My reference of “not allow me in” was due to the fact that I was “not a member“ of the group. I had a difficult time and ultimately, not able to learn how to either request, or add this group to my Google account, for access. When I followed the links to all the similar problems I found, they led to the Google Account. Again, it allowed me to only read maybe the first few sentences or post. It would not allow me to see the additional comments, and understand it further. Either from my lack of experience with the Subsurface set up, or not being able to identify how to or, what the name of the group was, to add to my Google account. I was unaware that I was using a developer emailing list. I came across an email that appeared to be a support email. I am not interested in having developer access. I’m sorry if my description came across garbled and confusing. I opened up Subsurface app on my computer to enter some logs. I noticed one of the logs and edited the name. If I recall correctly, I saved it to the cloud, and then I noticed I was missing a few dive logs. So then I entered a “test dive“ to see if there was a server updating concern. Upon entering it, I saved it to the cloud on my computer, and then it deleted all the other logs, and had just that one “test log”. As I said, in the other email, I know for sure I did not delete any dive logs. I believe I closed out the computer and opened my iPhone, and saw that the three or four were still missing the few dives, but had all the others there. So I synced it to the cloud, and then it deleted the rest of them, and only left me with the “test’ dive”. Yes, I would appreciate your help in restoring them and am giving explicit permission to help me in any way that you can. I understand this is a hobby, and would be okay if I had to just write it off and re-create it again, or even not use Subsurface, as my backup from herein. Understandably, I would like to know how to make sure I don’t create this scenario again. Thank you so much for taking the time to write here. I think you have a
Re: Subsurface-mobile support request / Lost Logs when synced to cloud
Hi Callie, It took about a solid hour of work, but I believe I have restored all of the deleted dives in your cloud account. Please refresh (ideally on all of your devices/computers) the cloud storage account to make sure everything is where you want it to be. I may have lost a dive site or two in the process (if I did, then it's for dives on Oct 7 and 8), but I think everything else should be back to normal. And to reiterate what I wrote before, to ensure that you don't get into this situation again, please ensure that you ALWAYS manually sync with the cloud storage before editing dives or downloading dives from a dive computer. Sorry for the inconvenience. /D > On Oct 15, 2023, at 17:23, Callie K wrote: > > Hello Dirk, > > Thank you for your email. > > First of all, I would like to thank you for the product/service and now > understand this is a hobby for a bunch of people. A great hobby! > > I’m sorry if my message came across as if there is a misunderstanding as to > what is happening. There was no anger outbursts directed towards the > developers, nor anger channeled in any direction whatsoever. Frustration with > the failure or under development, of what I now understand happened, yes. I > always recognize that there are bugs, issues, and unknowns that surface > continually and throughout our evolution of IT advancement. I am a solution > driven individual who understands things happen and always try to find > solutions, and then preventative measures. May be a better way for me to use > Subsurface. > > I think what I take from this, and your dramatic email, is that, a couple > websites so highly recommend your product/service without sharing, or me > recognizing, it is not a business level system. Also, lost data occurrences > frequently do happen with users, and there may be some under development > issues, and that’s okay. After this happened to me, I did Google everything > looking for a solution and found that it has a pattern that occurs more > frequently. > > I relied on it perhaps more than I was aware that I should have. And I have > no problem using a paid service, because, this information is rather > important in its’ nature for what I am using it for. > > As I said earlier here, I did Google the issue. I do have a Google account, > and in excellent standing. I am an upstanding citizen. My reference of “not > allow me in” was due to the fact that I was “not a member“ of the group. I > had a difficult time and ultimately, not able to learn how to either request, > or add this group to my Google account, for access. When I followed the links > to all the similar problems I found, they led to the Google Account. Again, > it allowed me to only read maybe the first few sentences or post. It would > not allow me to see the additional comments, and understand it further. > Either from my lack of experience with the Subsurface set up, or not being > able to identify how to or, what the name of the group was, to add to my > Google account. > > I was unaware that I was using a developer emailing list. I came across an > email that appeared to be a support email. I am not interested in having > developer access. > > I’m sorry if my description came across garbled and confusing. I opened up > Subsurface app on my computer to enter some logs. I noticed one of the logs > and edited the name. If I recall correctly, I saved it to the cloud, and then > I noticed I was missing a few dive logs. So then I entered a “test dive“ to > see if there was a server updating concern. Upon entering it, I saved it to > the cloud on my computer, and then it deleted all the other logs, and had > just that one “test log”. As I said, in the other email, I know for sure I > did not delete any dive logs. > > I believe I closed out the computer and opened my iPhone, and saw that the > three or four were still missing the few dives, but had all the others there. > So I synced it to the cloud, and then it deleted the rest of them, and only > left me with the “test’ dive”. > > Yes, I would appreciate your help in restoring them and am giving explicit > permission to help me in any way that you can. I understand this is a hobby, > and would be okay if I had to just write it off and re-create it again, or > even not use Subsurface, as my backup from herein. Understandably, I would > like to know how to make sure I don’t create this scenario again. > > Thank you so much for taking the time to write here. I think you have a great > product/service and I’m excited to see you continue to grow and evolve! Kudos > to all of you with your work and achievements with Subsurface. > > Thank you Dirk. > > Respectfully, > Callie > > > >> On Oct 15, 2023, at 12:53 PM, Dirk Hohndel wrote: >> >> >> The tone of your message makes me think that you are misunderstanding what >> is happening. >> >> (a) the Google group requires a Google account. But it shouldn't (and
Re: Subsurface-mobile support request / Lost Logs when synced to cloud
Hello Dirk, Thank you for your email. First of all, I would like to thank you for the product/service and now understand this is a hobby for a bunch of people. A great hobby! I’m sorry if my message came across as if there is a misunderstanding as to what is happening. There was no anger outbursts directed towards the developers, nor anger channeled in any direction whatsoever. Frustration with the failure or under development, of what I now understand happened, yes. I always recognize that there are bugs, issues, and unknowns that surface continually and throughout our evolution of IT advancement. I am a solution driven individual who understands things happen and always try to find solutions, and then preventative measures. May be a better way for me to use Subsurface. I think what I take from this, and your dramatic email, is that, a couple websites so highly recommend your product/service without sharing, or me recognizing, it is not a business level system. Also, lost data occurrences frequently do happen with users, and there may be some under development issues, and that’s okay. After this happened to me, I did Google everything looking for a solution and found that it has a pattern that occurs more frequently. I relied on it perhaps more than I was aware that I should have. And I have no problem using a paid service, because, this information is rather important in its’ nature for what I am using it for. As I said earlier here, I did Google the issue. I do have a Google account, and in excellent standing. I am an upstanding citizen. My reference of “not allow me in” was due to the fact that I was “not a member“ of the group. I had a difficult time and ultimately, not able to learn how to either request, or add this group to my Google account, for access. When I followed the links to all the similar problems I found, they led to the Google Account. Again, it allowed me to only read maybe the first few sentences or post. It would not allow me to see the additional comments, and understand it further. Either from my lack of experience with the Subsurface set up, or not being able to identify how to or, what the name of the group was, to add to my Google account. I was unaware that I was using a developer emailing list. I came across an email that appeared to be a support email. I am not interested in having developer access. I’m sorry if my description came across garbled and confusing. I opened up Subsurface app on my computer to enter some logs. I noticed one of the logs and edited the name. If I recall correctly, I saved it to the cloud, and then I noticed I was missing a few dive logs. So then I entered a “test dive“ to see if there was a server updating concern. Upon entering it, I saved it to the cloud on my computer, and then it deleted all the other logs, and had just that one “test log”. As I said, in the other email, I know for sure I did not delete any dive logs. I believe I closed out the computer and opened my iPhone, and saw that the three or four were still missing the few dives, but had all the others there. So I synced it to the cloud, and then it deleted the rest of them, and only left me with the “test’ dive”. Yes, I would appreciate your help in restoring them and am giving explicit permission to help me in any way that you can. I understand this is a hobby, and would be okay if I had to just write it off and re-create it again, or even not use Subsurface, as my backup from herein. Understandably, I would like to know how to make sure I don’t create this scenario again. Thank you so much for taking the time to write here. I think you have a great product/service and I’m excited to see you continue to grow and evolve! Kudos to all of you with your work and achievements with Subsurface. Thank you Dirk. Respectfully, Callie On Oct 15, 2023, at 12:53 PM, Dirk Hohndel wrote: The tone of your message makes me think that you are misunderstanding what is happening. (a) the Google group requires a Google account. But it shouldn't (and to the best of my knowledge doesn't) reject anyone who hasn't been banned from other groups for excessive abusive behavior in the past. (b) the developer mailing list that you tried sending an email to has been overrun with subscription spam and now requires explicit approval from me to add people - but I don't think that you want to be a developer from the way this all sounds (c) your description of what happens is garbled and confusing. Please try to explain in sequence what happened, how many devices / computers were involved, etc (d) any data that was at some point saved to the cloud (so that has successfully synced between two or more devices) is still there. You just managed to confuse the algorithm with the sequence of actions which resulted in it assuming that you wanted to replace old dives with new ones, instead of adding new ones. I'll repeat what I have said
Re: Subsurface-mobile support request / Lost Logs when synced to cloud
Hi Willem, Thank you for your email. I understand you were away, is there anyway of recovering my entire list of dives and reinstating before the one-month time, or even at all? Is there a link someone knows about that could be sent me for self help? Thank you so much! Thank, Callie On Oct 15, 2023, at 1:31 PM, Willem Ferguson wrote: I am currently overseas but when I get back I will read the user manual carefully and see how some explicit text could be added if it does not exist alteady. This 'problem' is common enough so that Dirk does not need to repeat the full explanation every time. I will make contact contact in about a month's time. Kind regards, Willem Sent from Proton Mail mobile Original Message On 15 Oct 2023, 18:53, Dirk Hohndel via subsurface < subsurface@subsurface-divelog.org> wrote: The tone of your message makes me think that you are misunderstanding what is happening. (a) the Google group requires a Google account. But it shouldn't (and to the best of my knowledge doesn't) reject anyone who hasn't been banned from other groups for excessive abusive behavior in the past. (b) the developer mailing list that you tried sending an email to has been overrun with subscription spam and now requires explicit approval from me to add people - but I don't think that you want to be a developer from the way this all sounds (c) your description of what happens is garbled and confusing. Please try to explain in sequence what happened, how many devices / computers were involved, etc (d) any data that was at some point saved to the cloud (so that has successfully synced between two or more devices) is still there. You just managed to confuse the algorithm with the sequence of actions which resulted in it assuming that you wanted to replace old dives with new ones, instead of adding new ones. I'll repeat what I have said in dozens of answers that your search found already. This is an open source project - a hobby for a bunch of people. Angry outbursts at the developers might work for a paid product (newsflash, they usually don't), but when attacking someone who wants to help you because it's something that they like to do, it generally tends to have the opposite effect. If you would like help, I need two things (a) your explicit permission to access your cloud data (because I never interact with user dive data without such explicit permission) (b) a good descriptions of which dives should be there (how many, what rough time frame are they from) and the sequence of events that made everything disappear - because I need to undo those events in the backend, and the more information I have on what happened, the easier that process will be. Finally, as to your question how to avoid this in the future - in about half of the cases the issues is that on a PC you downloaded new dives before opening the cloud storage and then ended up overwriting cloud storage. The other half are situation where you made changes on two different devices without syncing first. There are a couple of other scenarios, but they are very rare. The simple approach to preventing this issue is to simply always sync with the cloud FIRST, before making any changes (downloading new dives from a dive computer, editing dives, etc). /D > On Oct 14, 2023, at 21:04, Callie K wrote: > > Hello, > > I am very upset. All my data was lost from your app tonight. > > I edited one dive log, sync’d to the cloud, and it deleted four of them. Shortly there after, I wasn’t sure what happened and I added another dive log and sync’d it to the cloud again. This time I deleted all the remainder of my logs. There were about 40 dive logs. > > There is no way I deleted my dove log information, just no way. > > I googled this issue and saw numerous other posts about this problem. I even went over to your Google groups, but it would not allow me in, please explain how to access, that Google sector/forum. I wasn’t able to find any way to add that as a group, nor register. > > Please restore the data, your app deleted, hid, or re-distributed to another area. > > Also, please explain what caused this problem so as it can be avoided in the future. > > Thank you, > Callie > > > Please describe your issue here and keep the attached logs. > > > > > ___ 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-mobile support request / Lost Logs when synced to cloud
I am currently overseas but when I get back I will read the user manual carefully and see how some explicit text could be added if it does not exist alteady. This 'problem' is common enough so that Dirk does not need to repeat the full explanation every time. I will make contact contact in about a month's time. Kind regards, Willem Sent from Proton Mail mobile Original Message On 15 Oct 2023, 18:53, Dirk Hohndel via subsurface wrote: > The tone of your message makes me think that you are misunderstanding what is > happening. (a) the Google group requires a Google account. But it shouldn't > (and to the best of my knowledge doesn't) reject anyone who hasn't been > banned from other groups for excessive abusive behavior in the past. (b) the > developer mailing list that you tried sending an email to has been overrun > with subscription spam and now requires explicit approval from me to add > people - but I don't think that you want to be a developer from the way this > all sounds (c) your description of what happens is garbled and confusing. > Please try to explain in sequence what happened, how many devices / computers > were involved, etc (d) any data that was at some point saved to the cloud (so > that has successfully synced between two or more devices) is still there. You > just managed to confuse the algorithm with the sequence of actions which > resulted in it assuming that you wanted to replace old dives with new ones, > instead of adding new ones. I'll repeat what I have said in dozens of answers > that your search found already. This is an open source project - a hobby for > a bunch of people. Angry outbursts at the developers might work for a paid > product (newsflash, they usually don't), but when attacking someone who wants > to help you because it's something that they like to do, it generally tends > to have the opposite effect. If you would like help, I need two things (a) > your explicit permission to access your cloud data (because I never interact > with user dive data without such explicit permission) (b) a good descriptions > of which dives should be there (how many, what rough time frame are they > from) and the sequence of events that made everything disappear - because I > need to undo those events in the backend, and the more information I have on > what happened, the easier that process will be. Finally, as to your question > how to avoid this in the future - in about half of the cases the issues is > that on a PC you downloaded new dives before opening the cloud storage and > then ended up overwriting cloud storage. The other half are situation where > you made changes on two different devices without syncing first. There are a > couple of other scenarios, but they are very rare. The simple approach to > preventing this issue is to simply always sync with the cloud FIRST, before > making any changes (downloading new dives from a dive computer, editing > dives, etc). /D > On Oct 14, 2023, at 21:04, Callie K wrote: > > Hello, > > > I am very upset. All my data was lost from your app tonight. > > I edited one > dive log, sync’d to the cloud, and it deleted four of them. Shortly there > after, I wasn’t sure what happened and I added another dive log and sync’d it > to the cloud again. This time I deleted all the remainder of my logs. There > were about 40 dive logs. > > There is no way I deleted my dove log > information, just no way. > > I googled this issue and saw numerous other > posts about this problem. I even went over to your Google groups, but it > would not allow me in, please explain how to access, that Google > sector/forum. I wasn’t able to find any way to add that as a group, nor > register. > > Please restore the data, your app deleted, hid, or > re-distributed to another area. > > Also, please explain what caused this > problem so as it can be avoided in the future. > > Thank you, > Callie > > > > Please describe your issue here and keep the attached logs. > > > > > > ___ 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-mobile support request / Lost Logs when synced to cloud
The tone of your message makes me think that you are misunderstanding what is
happening.
(a) the Google group requires a Google account. But it shouldn't (and to the
best of my knowledge doesn't) reject anyone who hasn't been banned from other
groups for excessive abusive behavior in the past.
(b) the developer mailing list that you tried sending an email to has been
overrun with subscription spam and now requires explicit approval from me to
add people - but I don't think that you want to be a developer from the way
this all sounds
(c) your description of what happens is garbled and confusing. Please try to
explain in sequence what happened, how many devices / computers were involved,
etc
(d) any data that was at some point saved to the cloud (so that has
successfully synced between two or more devices) is still there. You just
managed to confuse the algorithm with the sequence of actions which resulted in
it assuming that you wanted to replace old dives with new ones, instead of
adding new ones.
I'll repeat what I have said in dozens of answers that your search found
already. This is an open source project - a hobby for a bunch of people. Angry
outbursts at the developers might work for a paid product (newsflash, they
usually don't), but when attacking someone who wants to help you because it's
something that they like to do, it generally tends to have the opposite effect.
If you would like help, I need two things
(a) your explicit permission to access your cloud data (because I never
interact with user dive data without such explicit permission)
(b) a good descriptions of which dives should be there (how many, what rough
time frame are they from) and the sequence of events that made everything
disappear - because I need to undo those events in the backend, and the more
information I have on what happened, the easier that process will be.
Finally, as to your question how to avoid this in the future - in about half of
the cases the issues is that on a PC you downloaded new dives before opening
the cloud storage and then ended up overwriting cloud storage. The other half
are situation where you made changes on two different devices without syncing
first. There are a couple of other scenarios, but they are very rare. The
simple approach to preventing this issue is to simply always sync with the
cloud FIRST, before making any changes (downloading new dives from a dive
computer, editing dives, etc).
/D
> On Oct 14, 2023, at 21:04, Callie K wrote:
>
> Hello,
>
> I am very upset. All my data was lost from your app tonight.
>
> I edited one dive log, sync’d to the cloud, and it deleted four of them.
> Shortly there after, I wasn’t sure what happened and I added another dive log
> and sync’d it to the cloud again. This time I deleted all the remainder of my
> logs. There were about 40 dive logs.
>
> There is no way I deleted my dove log information, just no way.
>
> I googled this issue and saw numerous other posts about this problem. I even
> went over to your Google groups, but it would not allow me in, please explain
> how to access, that Google sector/forum. I wasn’t able to find any way to add
> that as a group, nor register.
>
> Please restore the data, your app deleted, hid, or re-distributed to another
> area.
>
> Also, please explain what caused this problem so as it can be avoided in the
> future.
>
> Thank you,
> Callie
>
>
> Please describe your issue here and keep the attached logs.
>
>
>
>
>
"0.000: Successfully opened logfile
/var/mobile/Containers/Data/Application/C61B6173-EAEC-4239-95F3-9A3E5FAE8B5F/Documents/subsurface.log
at Sat Oct 14 22:22:14 2023"
"0.000: Starting Subsurface-mobile:3.4.7(5.0.9.33):iOS 16.6:arm64:en-US"
"0.000: built with libdivecomputer v0.8.0-devel-Subsurface-NG
(a17e466bd1d2e675666e20862182d618cf6d7190)"
"0.000: built with Qt Version 5.15.2, runtime from Qt Version 5.15.2"
"0.000: built with libgit2 1.0.1"
"0.000: Running on iOS 16.6"
discovery methods 2
starting BT/BLE discovery
QObject::connect(QUndoStack, QMLManager): invalid nullptr parameter
"0.015: download page -- looking for known BT/BLE device"
"0.018: [screensetup] width changed now 510 x 765 vs screen 428 x 926"
"0.018: [screensetup] window width changed to 510 orientation 1"
"0.018: [screensetup] remembering new orientation"
qrc:/qml/StatisticsPage.qml:142:4: QML TemplateSlimComboBox: Binding loop
detected for property "currentIndex"
qrc:/qml/StatisticsPage.qml:125:4: QML TemplateSlimComboBox: Binding loop
detected for property "currentIndex"
qrc:/qml/StatisticsPage.qml:108:4: QML TemplateSlimComboBox: Binding loop
detected for property "currentIndex"
"0.038: StartPage visibility changed to false"
"0.038: not yet initialized, show busy spinner"
"0.039: regular font size changed to 16"
qrc:/qml/DiveSummary.qml:33:2: QML Connections: Implicitly defined onFoo
properties in Connections are deprecated. Use this syntax instead: function
onFoo() { ... }
Re: Subsurface-mobile support request
Hey Jason,
I've just updated to version 10.66 via HWOS Config App for Android.
Jason Bramwell schrieb am Fr., 22. Mai 2020, 08:46:
> What version of the firmware is your dive computer running? I think there
> were some Bluetooth connectivity issues with certain older versions (I
> cannot recall the details of these). Current versions are hwOS Tech 3.10
> and hwOS Sport 10.66
>
> Sent from my iPhone
>
> On 22 May 2020, at 01:16, Till Schwab via subsurface <
> subsurface@subsurface-divelog.org> wrote:
>
>
> *Till - has this worked before with that OSTC? *
> This is my first OSTC and therefore the first time that I use the OSTC
> with subsurface.
>
> *Does the official HW downloader work? *
> What is the official HW downloader? As far as I know, there is only
> second-party software for OSTC Sport
>
>
> *And the obvious: does it help to reset the thing by turning it off and on
> again with removal of battery? *
> No, I just tested it. Unfortunately no improvement.
>
> By the way, the download / connection with the Windows 10 software also
> does not work (see jpg. in the appendix).
>
>
>
>
> Am Do., 21. Mai 2020 um 22:51 Uhr schrieb Linus Torvalds <
> torva...@linux-foundation.org>:
>
>> On Thu, May 21, 2020 at 1:30 PM Dirk Hohndel wrote:
>> >
>> > This looks like we are starting communication, but then all we get back
>> from the OSTC Sport is 0x
>> >
>> > Any ideas?
>>
>> The BLE side looks good and normal.
>>
>> >> Service discovery initiated
>> >> Found service "{1800--1000-8000-00805f9b34fb}"
>> >> .. ignoring standard service
>> >> Found service "{1801--1000-8000-00805f9b34fb}"
>> >> .. ignoring standard service
>> >> Found service "{180a--1000-8000-00805f9b34fb}"
>> >> .. ignoring standard service
>> >> Found service "{fefb--1000-8000-00805f9b34fb}"
>> >> .. recognized service Heinrichs-Weikamp
>> >> .. starting discovery
>> >> Discovery of "{fefb--1000-8000-00805f9b34fb}" started
>> >> .. done discovering services
>>
>> Ok, so this is triggering the new code that actually recognizes the
>> service ID, but for the case of the OSTC, that's actually not that
>> different from what it used to do (HW already had the special UUID
>> trigger).
>>
>> And it clearly does pick that service:
>>
>> >> Service "fefb--1000-8000-00805f9b34fb" discovered (start: 10
>> end: 22 ) QLowEnergyServicePrivate(0x6fd41feb50)
>> >> Found service "{fefb--1000-8000-00805f9b34fb}" "Unknown
>> Service"
>> >>c: "{0001--1000-8000-00802500}"
>> >> d: "{2902--1000-8000-00805f9b34fb}"
>> >>c: "{0002--1000-8000-00802500}"
>> >> d: "{2902--1000-8000-00805f9b34fb}"
>> >>c: "{0003--1000-8000-00802500}"
>> >> d: "{2902--1000-8000-00805f9b34fb}"
>> >>c: "{0004--1000-8000-00802500}"
>> >> d: "{2902--1000-8000-00805f9b34fb}"
>> >> Using service "{fefb--1000-8000-00805f9b34fb}" as preferred
>> service
>> >> .. enabling notifications
>>
>> looking good so far, and:
>>
>> >> Write descriptor with handle 22 "0200" (service:
>> "{fefb--1000-8000-00805f9b34fb}" )
>> >> Write characteristic with handle 17 "ff" (service:
>> "{fefb--1000-8000-00805f9b34fb}" , writeWithResponse: true ,
>> signed: false )
>> >> Descriptor write confirmation "{fefb--1000-8000-00805f9b34fb}"
>> 22 "0200" QLowEnergyService::NoError
>> >> BLE write completed
>> >> Descriptor write confirmation "{fefb--1000-8000-00805f9b34fb}"
>> 16 "0100" QLowEnergyService::NoError
>> >> BLE write completed
>> >> Characteristic write confirmation
>> "{fefb--1000-8000-00805f9b34fb}" 17 "ff" QLowEnergyService::NoError
>> >> Characteristic change notification
>> "{fefb--1000-8000-00805f9b34fb}" 20 "17"
>>
>> Yeah, IO is working and data is transferring. At least to begin with.
>>
>> The libdivecomputer log is more clear about the actual data transfer,
>> but they look fine too - all the way until it just starts sending all
>> FF (with then very occasional noise of other things that again look
>> like valid data).
>>
>> But that odd stream of FF doesn't _look_ like our BLE code would be
>> the cause of it. At least not the core code.
>>
>> It could be some artifact of the magical HW serial flow control code
>> (the whole "hw_credit" thing), but I do not know that code at all.
>> That was all Jan Mulder, I think. But none of that has changed lately.
>>
>> Till - has this worked before with that OSTC? Does the official HW
>> downloader work?
>>
>> And the obvious: does it help to reset the thing by turning it off and
>> on again with removal of battery?
>>
>> Linus
>>
>
> ___
> subsurface mailing list
> subsurface@subsurface-divelog.org
> http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
>
>
___
subsurface maili
Re: Subsurface-mobile support request
What version of the firmware is your dive computer running? I think there were
some Bluetooth connectivity issues with certain older versions (I cannot recall
the details of these). Current versions are hwOS Tech 3.10 and hwOS Sport 10.66
Sent from my iPhone
> On 22 May 2020, at 01:16, Till Schwab via subsurface
> wrote:
>
>
> Till - has this worked before with that OSTC?
> This is my first OSTC and therefore the first time that I use the OSTC with
> subsurface.
>
> Does the official HW downloader work?
> What is the official HW downloader? As far as I know, there is only
> second-party software for OSTC Sport
>
> And the obvious: does it help to reset the thing by turning it off and on
> again with removal of battery?
> No, I just tested it. Unfortunately no improvement.
>
> By the way, the download / connection with the Windows 10 software also does
> not work (see jpg. in the appendix).
>
>
>
>
>> Am Do., 21. Mai 2020 um 22:51 Uhr schrieb Linus Torvalds
>> :
>> On Thu, May 21, 2020 at 1:30 PM Dirk Hohndel wrote:
>> >
>> > This looks like we are starting communication, but then all we get back
>> > from the OSTC Sport is 0x
>> >
>> > Any ideas?
>>
>> The BLE side looks good and normal.
>>
>> >> Service discovery initiated
>> >> Found service "{1800--1000-8000-00805f9b34fb}"
>> >> .. ignoring standard service
>> >> Found service "{1801--1000-8000-00805f9b34fb}"
>> >> .. ignoring standard service
>> >> Found service "{180a--1000-8000-00805f9b34fb}"
>> >> .. ignoring standard service
>> >> Found service "{fefb--1000-8000-00805f9b34fb}"
>> >> .. recognized service Heinrichs-Weikamp
>> >> .. starting discovery
>> >> Discovery of "{fefb--1000-8000-00805f9b34fb}" started
>> >> .. done discovering services
>>
>> Ok, so this is triggering the new code that actually recognizes the
>> service ID, but for the case of the OSTC, that's actually not that
>> different from what it used to do (HW already had the special UUID
>> trigger).
>>
>> And it clearly does pick that service:
>>
>> >> Service "fefb--1000-8000-00805f9b34fb" discovered (start: 10 end:
>> >> 22 ) QLowEnergyServicePrivate(0x6fd41feb50)
>> >> Found service "{fefb--1000-8000-00805f9b34fb}" "Unknown Service"
>> >>c: "{0001--1000-8000-00802500}"
>> >> d: "{2902--1000-8000-00805f9b34fb}"
>> >>c: "{0002--1000-8000-00802500}"
>> >> d: "{2902--1000-8000-00805f9b34fb}"
>> >>c: "{0003--1000-8000-00802500}"
>> >> d: "{2902--1000-8000-00805f9b34fb}"
>> >>c: "{0004--1000-8000-00802500}"
>> >> d: "{2902--1000-8000-00805f9b34fb}"
>> >> Using service "{fefb--1000-8000-00805f9b34fb}" as preferred
>> >> service
>> >> .. enabling notifications
>>
>> looking good so far, and:
>>
>> >> Write descriptor with handle 22 "0200" (service:
>> >> "{fefb--1000-8000-00805f9b34fb}" )
>> >> Write characteristic with handle 17 "ff" (service:
>> >> "{fefb--1000-8000-00805f9b34fb}" , writeWithResponse: true ,
>> >> signed: false )
>> >> Descriptor write confirmation "{fefb--1000-8000-00805f9b34fb}" 22
>> >> "0200" QLowEnergyService::NoError
>> >> BLE write completed
>> >> Descriptor write confirmation "{fefb--1000-8000-00805f9b34fb}" 16
>> >> "0100" QLowEnergyService::NoError
>> >> BLE write completed
>> >> Characteristic write confirmation
>> >> "{fefb--1000-8000-00805f9b34fb}" 17 "ff"
>> >> QLowEnergyService::NoError
>> >> Characteristic change notification
>> >> "{fefb--1000-8000-00805f9b34fb}" 20 "17"
>>
>> Yeah, IO is working and data is transferring. At least to begin with.
>>
>> The libdivecomputer log is more clear about the actual data transfer,
>> but they look fine too - all the way until it just starts sending all
>> FF (with then very occasional noise of other things that again look
>> like valid data).
>>
>> But that odd stream of FF doesn't _look_ like our BLE code would be
>> the cause of it. At least not the core code.
>>
>> It could be some artifact of the magical HW serial flow control code
>> (the whole "hw_credit" thing), but I do not know that code at all.
>> That was all Jan Mulder, I think. But none of that has changed lately.
>>
>> Till - has this worked before with that OSTC? Does the official HW
>> downloader work?
>>
>> And the obvious: does it help to reset the thing by turning it off and
>> on again with removal of battery?
>>
>> Linus
>
>
> ___
> 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-mobile support request
On Thu, May 21, 2020 at 3:30 PM Till Schwab wrote: > > Till - has this worked before with that OSTC? > This is my first OSTC and therefore the first time that I use the OSTC with > subsurface. Ahh, ok, then it does sound like it might be a "corrupt memory" issue, possibly together with some parsing limitation of ours. Sending Jef a memory dump should clarify. > Does the official HW downloader work? > What is the official HW downloader? As far as I know, there is only > second-party software for OSTC Sport Heh. I've never used anything but subsurface, but I just assumed there was something else. I only used an OSTC a couple of times (years ago), my loaner was given to other people who needed it more. > And the obvious: does it help to reset the thing by turning it off and on > again with removal of battery? > No, I just tested it. Unfortunately no improvement. > > By the way, the download / connection with the Windows 10 software also does > not work (see jpg. in the appendix). Ok, that's just more verification that is almost certainly isn't the BLE communication itself (although the fact that your first try was android made it unlikely - I think that ends up being one of the more tested platforms wrt BLE and subsurface). Linus ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: Subsurface-mobile support request
Dirk, I don't see a description of the problem in the email thread, so I'm probably missing some context here. Anyway, from a quick inspection of the libdivecomputer logfile, the contents of the compact headers looks suspicious. The first 4 entries all look good: i=0, offset=0, current=1, data=C4160014011C101C1F1A1F0025010024 i=1, offset=16, current=2, data=9C14001405130A2368051C003A020024 i=2, offset=32, current=3, data=8417001405130D071C0621002F030024 i=3, offset=48, current=4, data=0F130014051310005A051A0015040024 The rest of the entries are all 0xFF, which is normal too. Except for the 228th entry: i=228, offset=3648, current=16386, data=0240812005408E400220608120024020 Because this one has the highest dive number (16386), it will be selected as the most recent dive. But that number looks very suspicious to me. I suspect it might be some corrupted data instead of an actual dive. So if we try to retrieve that dive, I wouldn't be surprised if things go wrong. I can't really tell what happened, because the log appears to be truncated at this point. @Till: Any chance you can download a full memory dump of your OSTC? You probably need to use the desktop version of subsurface for that. Or the libdivecomputer dctool command-line application. I'll likely also need the full log from a normal download. If this indeed turns out to be a corrupted logbook entry, then we can probably fix it by erasing the problematic logbook entry. Jef ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: Subsurface-mobile support request
On Thu, May 21, 2020 at 1:30 PM Dirk Hohndel wrote:
>
> This looks like we are starting communication, but then all we get back from
> the OSTC Sport is 0x
>
> Any ideas?
The BLE side looks good and normal.
>> Service discovery initiated
>> Found service "{1800--1000-8000-00805f9b34fb}"
>> .. ignoring standard service
>> Found service "{1801--1000-8000-00805f9b34fb}"
>> .. ignoring standard service
>> Found service "{180a--1000-8000-00805f9b34fb}"
>> .. ignoring standard service
>> Found service "{fefb--1000-8000-00805f9b34fb}"
>> .. recognized service Heinrichs-Weikamp
>> .. starting discovery
>> Discovery of "{fefb--1000-8000-00805f9b34fb}" started
>> .. done discovering services
Ok, so this is triggering the new code that actually recognizes the
service ID, but for the case of the OSTC, that's actually not that
different from what it used to do (HW already had the special UUID
trigger).
And it clearly does pick that service:
>> Service "fefb--1000-8000-00805f9b34fb" discovered (start: 10 end: 22
>> ) QLowEnergyServicePrivate(0x6fd41feb50)
>> Found service "{fefb--1000-8000-00805f9b34fb}" "Unknown Service"
>>c: "{0001--1000-8000-00802500}"
>> d: "{2902--1000-8000-00805f9b34fb}"
>>c: "{0002--1000-8000-00802500}"
>> d: "{2902--1000-8000-00805f9b34fb}"
>>c: "{0003--1000-8000-00802500}"
>> d: "{2902--1000-8000-00805f9b34fb}"
>>c: "{0004--1000-8000-00802500}"
>> d: "{2902--1000-8000-00805f9b34fb}"
>> Using service "{fefb--1000-8000-00805f9b34fb}" as preferred service
>> .. enabling notifications
looking good so far, and:
>> Write descriptor with handle 22 "0200" (service:
>> "{fefb--1000-8000-00805f9b34fb}" )
>> Write characteristic with handle 17 "ff" (service:
>> "{fefb--1000-8000-00805f9b34fb}" , writeWithResponse: true , signed:
>> false )
>> Descriptor write confirmation "{fefb--1000-8000-00805f9b34fb}" 22
>> "0200" QLowEnergyService::NoError
>> BLE write completed
>> Descriptor write confirmation "{fefb--1000-8000-00805f9b34fb}" 16
>> "0100" QLowEnergyService::NoError
>> BLE write completed
>> Characteristic write confirmation "{fefb--1000-8000-00805f9b34fb}"
>> 17 "ff" QLowEnergyService::NoError
>> Characteristic change notification "{fefb--1000-8000-00805f9b34fb}"
>> 20 "17"
Yeah, IO is working and data is transferring. At least to begin with.
The libdivecomputer log is more clear about the actual data transfer,
but they look fine too - all the way until it just starts sending all
FF (with then very occasional noise of other things that again look
like valid data).
But that odd stream of FF doesn't _look_ like our BLE code would be
the cause of it. At least not the core code.
It could be some artifact of the magical HW serial flow control code
(the whole "hw_credit" thing), but I do not know that code at all.
That was all Jan Mulder, I think. But none of that has changed lately.
Till - has this worked before with that OSTC? Does the official HW
downloader work?
And the obvious: does it help to reset the thing by turning it off and
on again with removal of battery?
Linus
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: Subsurface-mobile support request
On Fri, 2020-04-03 at 15:01 -0700, Linus Torvalds wrote: > On Fri, Apr 3, 2020 at 2:37 PM Dirk Hohndel via subsurface > wrote: > > I need to spend more time staring at the code to try to figure out > > how > > it's possible that we find two new dives but then believe that the > > dive > > list is unchanged - as THAT is the underlying problem here. Which > > is > > different from the problem we had with 3.0.x with x<3 where we > > thought > > that there was already a write ongoing and refused to start a > > "second" > > write... > > Hmm. "move_dive_table()" (which does the "move from download thread > to > main divelist) doesn't actually seem to do mark_divelist_changed(). So the UI code uses the undo mechanism to do this and it seems that either part of this code assumes that the other part of it marks the divelist changed. I'm still trying to make sure that I don't break unrelated things here, but I believe that I have identified where this goes sideways. The question now is where exactly to fix it. > So maybe that never happens, and then unsaved_changes() returns > false, > and then we don't even try to save anything? Yep. > Back to merging kernel ARM code for me.. You get to have all the fun :-) /D ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: Subsurface-mobile support request
On Fri, Apr 3, 2020 at 2:37 PM Dirk Hohndel via subsurface wrote: > > I need to spend more time staring at the code to try to figure out how > it's possible that we find two new dives but then believe that the dive > list is unchanged - as THAT is the underlying problem here. Which is > different from the problem we had with 3.0.x with x<3 where we thought > that there was already a write ongoing and refused to start a "second" > write... Hmm. "move_dive_table()" (which does the "move from download thread to main divelist) doesn't actually seem to do mark_divelist_changed(). So maybe that never happens, and then unsaved_changes() returns false, and then we don't even try to save anything? Back to merging kernel ARM code for me.. Linus ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: Subsurface-mobile support request
Marcus, I added the Subsurface developer mailing list because this worries me as it might affect more users... This test was done with the current Android beta: > Subsurface-mobile:3.0.3(4.9.3.1312):Android (10.0):arm64:sv-SE We can see a successful download of a couple of dives, but then when trying to save them, the dive list claims to be unchanged and have no unsaved changes - which then of course means that we lose the new dives after a program restart... I need to spend more time staring at the code to try to figure out how it's possible that we find two new dives but then believe that the dive list is unchanged - as THAT is the underlying problem here. Which is different from the problem we had with 3.0.x with x<3 where we thought that there was already a write ongoing and refused to start a "second" write... Thanks /D On Fri, 2020-04-03 at 23:27 +0200, Marcus Sundberg wrote: > "30.637: Dyk #1: ons 1 apr. 2020 17:49" > "37.683: Dyk #2: tis 31 mars 2020 14:45" > "46.356: Dyk #3: sön 29 mars 2020 14:25" > "46.358: Dyk sön 29 mars 2020 14:25 är redan nerladdat" > Deleting BLE object > Finishing download thread: 2 dives downloaded > "46.415: 2 dive downloaded" > "46.417: DCDownloadThread finished" > "610.535: AppState changed to inactive with no unsaved changes" > "610.587: AppState changed to suspended with no unsaved changes" > "704.343: AppState changed to active with no unsaved changes" > "705.671: Save downloaded dives that were selected" > "705.678: Record dives" > index 2 select changed to false > "705.766: local save requested with no unsaved changes" > "705.766: pageStack popping Download page" > "705.767: pageStack switched to DiveList" ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: Subsurface-mobile support request
How did you import those dives? /D > On Jan 27, 2020, at 5:01 PM, Kimberley Shirley > wrote: > > Hi > > I recently imported my dive log on the subsurface (desktop version) and all > my depths have been messed up. > > The import misread my metric depths as imperial so a dive to 30 metres is > being read as 30 ft and 8metres. > > Is there anyway I can fix this so the correct depth is recorded? > > Regards > Kimberley ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
