> On Oct 6, 2019, at 10:24 AM, John Smith wrote:
>
> I think you might have touched on something when you asked what device I have
> and mentioned the 64bit builds.
>
> It’s a Hudl- made for the Uk market a few years ago and now no longer
> supported. - hence being stuck on 5.x.
>
> I
I think you might have touched on something when you asked what device I have
and mentioned the 64bit builds.
It’s a Hudl- made for the Uk market a few years ago and now no longer
supported. - hence being stuck on 5.x.
I didn’t know what chip set I had, so ran CPU-z last night and discovered I
Excellent - I'm glad this is working or you!
/D
> On Oct 4, 2019, at 3:27 PM, Berthold Cogel wrote:
>
> On 04.10.19 22:01, Dirk Hohndel wrote:
>> New Beta version is available in Google Play.
>> There is a documented workaround for this which requires 5.12.5 or 5.13 - so
>> I switched our
On 04.10.19 22:01, Dirk Hohndel wrote:
New Beta version is available in Google Play.
There is a documented workaround for this which requires 5.12.5 or 5.13
- so I switched our Android binaries to be 5.13.1 based.
I'll push the straight forward changes in a little while, I first wanted
to get
> On Sep 27, 2019, at 11:13 AM, Anton Lundin wrote:
>
> On 27 September, 2019 - Dirk Hohndel wrote:
>
>> I haven't used the emulators in I don't know how long so I didn't even think
>> about this option. Oops.
>>
> ...
>>
>> I haven't tried an Android-x86_64 build - I think ever. I used to
On 27 September, 2019 - Dirk Hohndel wrote:
> I haven't used the emulators in I don't know how long so I didn't even think
> about this option. Oops.
>
...
>
> I haven't tried an Android-x86_64 build - I think ever. I used to build x86 a
> long time ago but stopped that as well.
> I'll try
On 27 September, 2019 - Dirk Hohndel wrote:
> Looking at John's log file a little more, here's something that really
> confuses me:
>
> QSslSocket: cannot resolve OPENSSL_init_ssl
> QSslSocket: cannot resolve OPENSSL_init_crypto
> ...
> QSslSocket: cannot resolve OpenSSL_version
> Incompatible
This looks complete.
And it makes me wonder about a couple of things...
> On Sep 27, 2019, at 8:15 AM, John Smith wrote:
> 09-27 16:10:07.097 538-577/? I/PackageManager: Running dexopt on:
> /data/app/org.subsurfacedivelog.mobile-1/base.apk
> pkg=org.subsurfacedivelog.mobile isa=x86
INFO: "54.362:
AppState changed to inactive with no save ongoing and no unsaved changes"
09-27 16:11:17.055 5567-5620/?
D//android/subsurface/qt-models/messagehandlermodel.cpp: INFO: "54.378:
AppState changed to suspended with no save ongoing and no unsaved changes"
09-27 16:11:18
Looking at John's log file a little more, here's something that really confuses
me:
QSslSocket: cannot resolve OPENSSL_init_ssl
QSslSocket: cannot resolve OPENSSL_init_crypto
...
QSslSocket: cannot resolve OpenSSL_version
Incompatible version of OpenSSL
We are bundling libssl.so in the .apk. So
> On Sep 27, 2019, at 6:08 AM, Anton Lundin wrote:
>>>
>>> So I didn't find an Android 5.0 devices (and I have so many devices, it's
>>> ridiculous), but I found a Nexus 10 with Android 5.1 and that happily syncs
>>> with the cloud... So yes, I'd love to see an actual log that shows us what's
On 27 September, 2019 - John Smith wrote:
> Please see attached
Great, there we see that it can't load libssl for some reason.
What would be even better were if you could hook up adb to your tablet
and extract a log that way. That can give us information from the OS
side, why it can't load the
Please see attached
On 26 Sep 2019, at 17:19, Dirk Hohndel
mailto:d...@hohndel.org>> wrote:
I didn't think it would even install on Android 5.0... but looking through the
Google Play stats we do in fact appear to have about 50 users on that version.
Interesting.
I have no idea how I would make
On 27 September, 2019 - Anton Lundin wrote:
> On 26 September, 2019 - Dirk Hohndel wrote:
>
> >
> > > On Sep 26, 2019, at 1:49 PM, Anton Lundin wrote:
> > >
> > > On 26 September, 2019 - Dirk Hohndel wrote:
> > >
> > >> I didn't think it would even install on Android 5.0... but looking
> >
On 26 September, 2019 - Dirk Hohndel wrote:
>
> > On Sep 26, 2019, at 1:49 PM, Anton Lundin wrote:
> >
> > On 26 September, 2019 - Dirk Hohndel wrote:
> >
> >> I didn't think it would even install on Android 5.0... but looking through
> >> the Google Play stats we do in fact appear to have
> On Sep 26, 2019, at 1:49 PM, Anton Lundin wrote:
>
> On 26 September, 2019 - Dirk Hohndel wrote:
>
>> I didn't think it would even install on Android 5.0... but looking through
>> the Google Play stats we do in fact appear to have about 50 users on that
>> version.
>> Interesting.
>> I
On 26 September, 2019 - Dirk Hohndel wrote:
> I didn't think it would even install on Android 5.0... but looking through
> the Google Play stats we do in fact appear to have about 50 users on that
> version.
> Interesting.
> I have no idea how I would make Subsurface support different openssl
> I didn't think it would even install on Android 5.0... but looking
> through the Google Play stats we do in fact appear to have about 50
> users on that version.
>
My Samsung T310 (8" Tablet) with Android 4.4.2 runs Subsurface 4.8.4 but
doesn't seem to get updates an more. But it still syncs
I didn't think it would even install on Android 5.0... but looking through the
Google Play stats we do in fact appear to have about 50 users on that version.
Interesting.
I have no idea how I would make Subsurface support different openssl versions.
Can you send the log - I'll dig around to see
Ive finally got my old android tablet running again and tried to get Subsurface
on it.
Using the latest version, it installs ok, seems to run well, but cannot connect
to the Cloud.
Looking into the developers log, the problem is that it cannot resolve OPENSSL
and the TLS fails.
Other than
20 matches
Mail list logo
