On Sat, Feb 06, 2016 at 07:15:38AM +1100, Rick Walsh wrote: > On 6 February 2016 at 06:46, Dirk Hohndel <[email protected]> wrote: > > > On Sat, Feb 06, 2016 at 06:27:00AM +1100, Rick Walsh wrote: > > > > > > > > So no simple fix that I'm aware of. > > > > > > > My build of 766 doesn't crash on my Samsung, but yours does (as does > > 774). > > > I thought the difference was Qt5.5 vs Qt5.6, but I just realized what > > might > > > be a more substantial difference in our builds. > > > > > > I tend to run the build script only periodically. Most of the time, > > > especially when working on a patch, I'll just run make inside the build > > > dir. So, my version will be a few commits behind in the Plasma > > > mobilecomponents. I suspect the crashes I get reliably might be linked > > to a > > > recent commit mobilecomponents change. I'll do some testing and report > > back. > > > > > > Here's to hoping it's an easy fix. > > > > Always :-) > > > > I was one mobilecomponents commit behind, 42c5562 'Make the (physical) back > button work again for the application window's pagestack'. I updated and > rebuilt the apk, but that version didn't crash for me. > > Note, there's another, minutes-old commit to mobilecomponents, 535e26f > 'don't make space for keyboard on Android'. It didn't cause or prevent a > crash for me, but maybe it fixes keyboard issues for others? > > In summary, it doesn't look like the mobilecomponents changes are related > to my crashes.
That was my assumption :-/ > > I can easily create a Qt5.5.1 based build for cross testing. Let me know. > > > > Please do. It sounds much easier than me building Qt5.6 master. I'm > interested to compare the latest subsurface-mobile built with both versions > on the same machine. OK, new build coming up. /D _______________________________________________ subsurface mailing list [email protected] http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
