> On Sep 27, 2019, at 11:13 AM, Anton Lundin <gla...@acc.umu.se> 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 build x86 
>> a long time ago but stopped that as well.
>> I'll try the ARM7 Android 5.0 simulator to see if I can reproduce John's 
>> problem - I realize that almost all my testing is on ARM64 these days - but 
>> my Android 5.1 tablet is ARM7 as well, just as the device he produced the 
>> log from.
>> 
>> Thanks for your help tracking this down, Anton!
> 
> The huge upside with android-x86/x86_x64 is that you can run the
> emulator with hardware acceleration. The arm emulator is just so slow
> that its unusable with modern android.
> 

I always remembered it as being painful.
But my bigger issue is that I have a device that seems to match the one 
exhibiting the problem for John - same architecture, same Android version. And 
that one seems to work just fine.
So I'm not sure that the emulator would show the problem to me, either.

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

Reply via email to