Subsurface-mobile

[Anton Lundin]

I think all the bits are still there so you can build a x86 android
binary yourself. I use them quite often when I debug things on the
emulator.

//Anton

On 11 September, 2016 - brossmeisl wrote:

> Dirk,
>     Fair enough. Not a problem. Thanks for the time and I am still very
> impressed with what you guys are doing.
> 
> On Sep 11, 2016 01:08, "Dirk Hohndel" <dirk at hohndel.org> wrote:
> 
> > Ha. I've stopped supporting x86 devices ages ago. Way too much work for no
> > significant user base. Sorry.
> >
> > /D
> >
> > On Sep 10, 2016, at 9:52 PM, brossmeisl <brian.rossmeisl at gmail.com> wrote:
> >
> > Oh. I am running an intel atom phone asus zenfone 2. It looks like its
> > trying to load an arm ssl lib. Do you mind adding 32bit intel support?
> >
> > On Sep 11, 2016 00:41, "brossmeisl" <brian.rossmeisl at gmail.com> wrote:
> >
> >> I am not a developer but it looks like it can't load some ssl lib
> >>
> >> 09-11 00:39:28.489 21209 21209 D houdini : [21209] Load library
> >> /data/app/org.subsurfacedivelog.mobile-1/lib/arm/libssl.so failed.
> >> 09-11 00:39:28.490 21209 21209 W System.err: Caused by:
> >> java.lang.UnsatisfiedLinkError: dlopen failed:
> >> "/data/app/org.subsurfacedivelog.mobile-1/lib/arm/libssl.so" has
> >> unexpected e_machine: 40
> >> 09-11 00:39:28.720   618   638 I ActivityManager: Displayed
> >> org.subsurfacedivelog.mobile/org.qtproject.qt5.android.bindings.QtActivity:
> >> +672ms
> >> 09-11 00:39:32.046   618  1553 I ActivityManager: START u0
> >> {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER]
> >> flg=0x10200000 cmp=org.subsurfacedivelog.mobi
> >> le/org.qtproject.qt5.android.bindings.QtActivity (has extras)} from uid
> >> 10035 on display 0
> >> 09-11 00:39:32.149 21209 21209 D houdini : [21209] Load library
> >> /data/app/org.subsurfacedivelog.mobile-1/lib/arm/libssl.so failed.
> >> 09-11 00:39:32.151 21209 21209 W System.err: Caused by:
> >> java.lang.UnsatisfiedLinkError: dlopen failed:
> >> "/data/app/org.subsurfacedivelog.mobile-1/lib/arm/libssl.so" has
> >> unexpected e_machine: 40
> >> 09-11 00:39:32.282   618   638 I ActivityManager: Displayed
> >> org.subsurfacedivelog.mobile/org.qtproject.qt5.android.bindings.QtActivity:
> >> +204ms
> >>
> >>
> >> On Sun, Sep 11, 2016 at 12:29 AM, Dirk Hohndel <dirk at hohndel.org> wrote:
> >>
> >>> Can you connect your phone to a computer via USB, turn on USB debugging
> >>> on the phone and use adb on the computer to extract the logcat output?
> >>>
> >>> /D
> >>> --
> >>> Sent from my phone
> >>>
> >>>
> >>> On September 10, 2016 9:26:40 PM PDT, brossmeisl <
> >>> brian.rossmeisl at gmail.com> wrote:
> >>>>
> >>>> I am getting "your application encountered a fatal error and cannot
> >>>> continue" when I try to start subsurface-mobile on my 6.0.1 marshmallow
> >>>> phone. I applied to be a beta tester and it still seems to happen there
> >>>> too. Do you have any recommendations? Thank you in advance.
> >>>>       Regards,
> >>>> Brian Rossmeisl
> >>>>
> >>>
> >>
> >

> _______________________________________________
> subsurface mailing list
> subsurface at subsurface-divelog.org
> http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface


-- 
Anton Lundin	+46702-161604