> On Dec 27, 2015, at 10:49 AM, Willem Ferguson > <[email protected]> wrote: > > On 27/12/2015 17:48, Dirk Hohndel wrote: >> Like with the other bugs >> a) once I can reproduce them, I'm much more likely to fix them. And this one >> I don't see on ANY of my devices (and I have quite a pile by now) >> b) would someone PLEASE be able to provide me the adb logcat output when >> this happens? >> >> > > Subsurface-mobile 4.5.2.498 running on Android 4.3 > > Below is the logcat for part of the execution. See the 2nd last line of this > shortened log. I have the complete log, this is grep output for "surface" in > the logcat. > Entry of cloud credentials with symptoms as discussed in previous email. > When SAVE is selected, dive list is loaded but screen freezes. Does not hang > OS, can close app. > > Hope this is helpful.
It doesn't make me go "Ahhhhh! That's it!" but it's progress. > D/Subsurface( 8351): (null):0 ((null)): can't find Qt localization for locale > "en-GB" searching in > "/work/build/______________________________PADDING______________________________/translations" > D/Subsurface( 8351): (null):0 ((null)): can't find Subsurface localization > for locale "en-GB" So here's of course one difference - you're running with en-GB while I'm running with en-US. I don't think this is what causes the problem, but who knows. I'll try switching my phone to a different locale. > W/Subsurface( 8351): (null):0 ((null)): QFont::setPointSizeF: Point size <= 0 > (-1.000000), must be greater than 0 > D/Subsurface( 8351): (null):0 ((null)): Starting > "Subsurface-mobile:4.5.2.498:Android 4.3:arm:en-GB" > > // Start entering cloud credentials > //==================================== > > D/Subsurface( 8351): (null):0 ((null)): verbose is 1 > W/Subsurface( 8351): qrc:///qml/main.qml:113 ((null)): > qrc:///qml/main.qml:113:5: QML Action: Binding loop detected for property > "checked" I saw this one as well, need to figure out what I did wrong there :-) > W/Subsurface( 8351): (null):0 ((null)): QObject::startTimer: Timers cannot be > started from another thread > W/Subsurface( 8351): (null):0 ((null)): QObject::startTimer: Timers cannot be > started from another thread > W/Subsurface( 8351): (null):0 ((null)): QObject::startTimer: Timers cannot be > started from another thread > W/Subsurface( 8351): (null):0 ((null)): QObject::startTimer: Timers cannot be > started from another thread > W/Subsurface( 8351): (null):0 ((null)): QObject::startTimer: Timers cannot be > started from another thread These have been around since forever - still no idea which timer is in the wrong thread :-( > D/Subsurface( 8351): (null):0 ((null)): called getUserid Dang - there's nothing else, no other warning. I need to add debugging output to show the state of the "show password" setting - maybe that's the issue. > // Credentials completed. > // Starting to load dive log... > // ============================== > > D/Subsurface( 8351): (null):0 ((null)): "received > WebserviceID:BICC730KZ97TYNPLV3YB0T9H16EONG" > D/Subsurface( 8351): (null):0 ((null)): cloud URL set as > "https://cloud.subsurface-divelog.org//git/[email protected][[email protected]]" > W/Subsurface( 8351): (null):0 ((null)): Cloud storage: checking connection to > cloud server > I/WindowManager( 2353): Screen frozen for +807ms due to Window{441d0448 u0 > org.subsurfacedivelog.mobile/org.qtproject.qt5.android.bindings.QtActivity} So this is most likely a really slow internet connection and things just hanging. It shouldn't because this should be running in a different thread, but clearly my grasp of what is running in which thread isn't as good as it should be. > W/Subsurface( 8351): qrc:///qml/DiveList.qml:17 ((null)): > qrc:///qml/DiveList.qml:17:3: QML ListItem: Binding loop detected for > property "width" Another loop. I don't think I've seen this one before. Thanks! /D _______________________________________________ subsurface mailing list [email protected] http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
