Re: towards 4.9.4

2020-04-11 Thread Chirana Gheorghita Eugeniu Theodor via subsurface
Ok. I will send email. The phone says it is not safe to install and I choose install anyway. I uninstall the beta and install the ci. support mail in a minute On Sun, Apr 12, 2020, 01:42 Dirk Hohndel wrote: > Playstore. Hmm. So are you talking Android then? > The Android build from CI isn't

Re: towards 4.9.4

2020-04-11 Thread Dirk Hohndel via subsurface
Playstore. Hmm. So are you talking Android then? The Android build from CI isn't signed, so your phone should either reject it or install it as a different app. Which means it shouldn't be able to access your settings. Which might affect your ability to get to your dives? Can you re-install the

Re: towards 4.9.4

2020-04-11 Thread Chirana Gheorghita Eugeniu Theodor via subsurface
So, Installed new vers from ci-release and no dives appear. uninstalled and reinstalled lates beta on playstore... all dives are back to normal. On Sun, Apr 12, 2020, 01:11 Dirk Hohndel wrote: > No it doesn't, the new storage can be tested by people who are curious. > You need to compile from

Re: towards 4.9.4

2020-04-11 Thread Dirk Hohndel via subsurface
No it doesn't, the new storage can be tested by people who are curious. You need to compile from source and use cloud2.subsurface-divecomputer.org as URL The back end is designed to keep the two servers in sync. But that needs lots more testing. If your cloud data is in fact missing, let me

Re: towards 4.9.4

2020-04-11 Thread Chirana Gheorghita Eugeniu Theodor via subsurface
Good, So the new vers 4.9.3.1432 uses different cloud storage? Because I just installed from ci-release and my heart stopped for a moment. 0 dives on cloud storage. On Sat, Apr 11, 2020, 21:26 Dirk Hohndel via subsurface < subsurface@subsurface-divelog.org> wrote: > > It's been forever (well,

towards 4.9.4

2020-04-11 Thread Dirk Hohndel via subsurface
It's been forever (well, just over seven months and about 1400 commits) since our last desktop release. I think I have all the outstanding PRs merged (and I just noticed that GitHub apparently lost our default settings for rebased-merges in the last couple of days and now we are back to having