No more menu button on Android app

[David Heim]

Hi, I have been using the android app for a while and have not encountered problems so far.

But yesterday when I opened the app after some flickering the dive log page came up. However the main menu button does not appear anymore and therefore I cannot any other features of the app (see screenshot).

Any fixes?

Thank you

[Stuart Vernon]

I am getting the same behavior. No way to access the main menu.

 

Also, I see other things that I think are issues:

 

• No dive # displayed next to the dives in the Dive list.
• When I tap a dive to open it it is displaying “wider” than my actual screen/display. For example, I cannot see the Map It button. But, if I swipe the dive slowly to the left the Map it button, dive #, and other things that are supposed to appear on the right side of the screen come into view. But, when I take my finger off the screen, the displayed dive either snaps back to the right or rolls further to the left, showing the next dive. Regardless, I do not have access to the Map It button and can only see things like the dive #, Water Temp, and SAC by pulling the dive over to the left and holding.
• If I scroll all the way to the bottom of the Dive List, the last dive is displayed with the system button bar covering half of it.

 

This is with Subsurface-mobile (Beta) Version 2.2.1 (4.9.3.30). Running on a Samsung Galaxy Note 8 running Android version 9.

--
You received this message because you are subscribed to the Google Groups "Subsurface Divelog" group.
To unsubscribe from this group and stop receiving emails from it, send an email to subsurface-dive...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/subsurface-divelog/14c74c2e-ee27-486b-a6f4-67e03e8676e7%40googlegroups.com.

[Dirk Hohndel]

It appears that a fix that solves a UI layout problem on a number of devices causes a regression on a small number of different devices. It's not quite clear to me how to make things work on all of them.

In most cases where this problem now appeared, turning your phone sideways, waiting for Subsurface-mobile to redraw its screen and then turning it into portrait mode again appears to be a workaround that get you the correct screen layout.

Please try this, and if it works, afterwards tap the menu, tap About, tap the button, copy the log files and send them to me.

Thanks

/D

To view this discussion on the web visit https://groups.google.com/d/msgid/subsurface-divelog/56F959AA-1BEB-4100-8B46-7FBD71CF27CB%40force2.net.

[Adric Norris]

That did indeed do the trick for me.

---------- subsurface.log ----------

"0.005: Successfully opened logfile /storage/emulated/0/subsurface.log at Mon Sep 23 01:15:54 2019"

"0.005: Starting Subsurface-mobile:2.2.1(4.9.3.30):Android  (10.0):arm64:en-US"

"0.005: built with libdivecomputer v0.7.0-devel-Subsurface-NG (ce6d9896a79afaa82641132e338f8744714c8593)"

"0.005: built with Qt Version 5.12.4, runtime from Qt Version 5.12.4"

"0.005: built with libgit2 0.26.0"

"0.005: Running on Android  (10.0)"

"0.005: Pixel 3 XL/google/crosshatch"

BTDiscoveryReDiscover: localBtDevice.isValid() true

"BTDiscoveryReDiscover: localDevice yuzuki is powered on, starting discovery"

paired BT classic device type 3 with address "00:11:77:46:6F:C1"

paired BLE device type 3 with address "LE:00:11:77:46:6F:C1"

paired BT classic device type 1 with address "0C:E0:E4:48:C3:EB"

paired BLE device type 2 with address "LE:AC:9A:22:B0:61:DE"

paired BT classic device type 1 with address "FC:58:FA:8D:01:23"

paired BT classic device type 1 with address "08:EB:ED:64:B3:B1"

paired BT classic device type 1 with address "10:0F:18:10:4D:9E"

paired BLE device type 2 with address "LE:C5:11:36:12:8B:DF"

paired BT classic device type 1 with address "90:B6:86:96:50:99"

paired BLE device type 2 with address "LE:00:13:43:54:8C:65"

Found new device: "Carista" "00:11:77:46:6F:C1"

Not recognized as dive computer

Found new device: "Carista" "LE:00:11:77:46:6F:C1"

Not recognized as dive computer

Found new device: "Savi 7xx" "0C:E0:E4:48:C3:EB"

Not recognized as dive computer

Found new device: "DCQQFP" "LE:AC:9A:22:B0:61:DE"

Not recognized as dive computer

Found new device: "BOHM B-66" "FC:58:FA:8D:01:23"

Not recognized as dive computer

Found new device: "SoundCore 2" "08:EB:ED:64:B3:B1"

Not recognized as dive computer

Found new device: "Motorola H730" "10:0F:18:10:4D:9E"

Not recognized as dive computer

Found new device: "Descent Mk1" "LE:C5:11:36:12:8B:DF"

Not recognized as dive computer

Found new device: "CAR MULTIMEDIA" "90:B6:86:96:50:99"

Not recognized as dive computer

Found new device: "G2" "LE:00:13:43:54:8C:65"

"this could be a Scubapro G2"

Paired = "Carista" "00:11:77:46:6F:C1"

Paired = "Carista" "LE:00:11:77:46:6F:C1"

Paired = "Savi 7xx" "0C:E0:E4:48:C3:EB"

Paired = "DCQQFP" "LE:AC:9A:22:B0:61:DE"

Paired = "BOHM B-66" "FC:58:FA:8D:01:23"

Paired = "SoundCore 2" "08:EB:ED:64:B3:B1"

Paired = "Motorola H730" "10:0F:18:10:4D:9E"

Paired = "Descent Mk1" "LE:C5:11:36:12:8B:DF"

Paired = "CAR MULTIMEDIA" "90:B6:86:96:50:99"

Paired = "G2" "LE:00:13:43:54:8C:65"

"Created position source android"

"0.020: Created position source android"

"Set GPS service update interval to 300 s"

"0.020: Set GPS service update interval to 300 s"

"0.021: location service is available"

qrc:/org/kde/kirigami/Page.qml:276:5: QML Loader: Binding loop detected for property "active"

Window width changed to 660

Column width 660 root item width 660

width in Grid Units 30 original gridUnit 22 now 22

QQmlExpression: Expression qrc:/qml/DownloadFromDiveComputer.qml:339:5 depends on non-NOTIFYable properties:

    QMLManager::DC_forceDownload

Model size of -1 is less than 0

"0.387: Synchronising data file"

"0.396: Load dives from local cache"

"0.556: Successfully opened dive data"

"0.571: AppState changed to active with save ongoing and no unsaved changes"

"0.573: 231 dives loaded from cache"

"0.574: have cloud credentials, but user asked not to connect to network"

Running on   

Window width changed to 411

Column width 411 root item width 411

width in Grid Units 21 original gridUnit 22 now 19

Window width changed to 570

Column width 570 root item width 570

width in Grid Units 30 original gridUnit 19 now 19

checkPendingIntents 

Column width 570 root item width 570

width in Grid Units 30 original gridUnit 19 now 19

Using the following font: Roboto at 15.545454545454545pt with mobile_scale: 1.15

qqwindow devicePixelRatio 3.5015 3.5015

Supported dive computers:

"Aeris: 500 AI (SERIAL), A300 (SERIAL), A300 AI (SERIAL), A300CS (SERIAL), Atmos 2 (SERIAL), Atmos AI (SERIAL), Atmos AI 2 (SERIAL), Compumask (SERIAL), Elite (SERIAL), Elite T3 (SERIAL), Epic (SERIAL), F10 (SERIAL), F11 (SERIAL), Manta (SERIAL), XR-1 NX (SERIAL), XR-2 (SERIAL)"

"Aqualung: i200 (SERIAL), i200C (SERIAL, BLE), i300 (SERIAL), i300C (SERIAL, BLE), i450T (SERIAL), i550 (SERIAL), i550C (SERIAL, BLE), i750TC (SERIAL, BT), i770R (SERIAL, BLE)"

"Atomic Aquatics: Cobalt (USB), Cobalt 2 (USB)"

"Beuchat: Mundial 2 (SERIAL), Mundial 3 (SERIAL), Voyager 2G (SERIAL)"

"Cochran: Commander I (SERIAL), Commander II (SERIAL), Commander TM (SERIAL), EMC-14 (SERIAL), EMC-16 (SERIAL), EMC-20H (SERIAL)"

"Cressi: Cartesio (SERIAL), Drake (SERIAL), Giotto (SERIAL), Goa (SERIAL), Leonardo (SERIAL), Newton (SERIAL)"

"Deepblu: Cosmiq+ (BLE)"

"DiveSystem: Orca (SERIAL), iDive DAN (SERIAL), iDive Deep (SERIAL), iDive Easy (SERIAL), iDive Free (SERIAL), iDive Pro (SERIAL), iDive Reb (SERIAL), iDive Stealth (SERIAL), iDive Tech (SERIAL), iDive X3M (SERIAL)"

"Garmin: Descent Mk1 (USBSTORAGE)"

"Genesis: React Pro (SERIAL), React Pro White (SERIAL)"

"Heinrichs Weikamp: Frog (SERIAL, BT), OSTC (SERIAL), OSTC 2 (SERIAL, BT, BLE), OSTC 2 TR (SERIAL, BT, BLE), OSTC 2C (SERIAL), OSTC 2N (SERIAL), OSTC 3 (SERIAL), OSTC 4 (SERIAL, BT, BLE), OSTC Mk2 (SERIAL), OSTC Plus (SERIAL, BT, BLE), OSTC Sport (SERIAL, BT, BLE), OSTC cR (SERIAL)"

"Hollis: DG02 (SERIAL), DG03 (SERIAL), TX1 (SERIAL)"

"Mares: Genius (SERIAL, BLE), Puck Pro (SERIAL, BLE), Quad (SERIAL, BLE), Quad Air (SERIAL, BLE), Smart (SERIAL, BLE), Smart Air (SERIAL, BLE), Smart Apnea (SERIAL, BLE)"

"Oceanic: Atom 1.0 (SERIAL), Atom 2.0 (SERIAL), Atom 3.0 (SERIAL), Atom 3.1 (SERIAL), Datamask (SERIAL), F10 (SERIAL), F11 (SERIAL), Geo (SERIAL), Geo 2.0 (SERIAL), Geo 4.0 (SERIAL, BLE), OC1 (SERIAL), OCS (SERIAL), OCi (SERIAL), Pro Plus 2 (SERIAL), Pro Plus 2.1 (SERIAL), Pro Plus 3 (SERIAL), Pro Plus X (SERIAL, BLE), VT 4.1 (SERIAL), VT Pro (SERIAL), VT3 (SERIAL), VT4 (SERIAL), VTX (SERIAL), Veo 1.0 (SERIAL), Veo 180 (SERIAL), Veo 2.0 (SERIAL), Veo 200 (SERIAL), Veo 250 (SERIAL), Veo 3.0 (SERIAL), Versa Pro (SERIAL)"

"Ratio: iDive Color Deep (SERIAL), iDive Color Easy (SERIAL), iDive Color Fancy (SERIAL), iDive Color Free (SERIAL), iDive Color Pro (SERIAL), iDive Color Reb (SERIAL), iDive Color Tech+ (SERIAL), iDive Deep (SERIAL), iDive Easy (SERIAL), iDive Fancy (SERIAL), iDive Free (SERIAL), iDive Pro (SERIAL), iDive Reb (SERIAL), iDive Tech+ (SERIAL), iX3M GPS Deep (SERIAL, BT), iX3M GPS Easy (SERIAL, BT), iX3M GPS Fancy (SERIAL, BT), iX3M GPS Pro  (SERIAL, BT), iX3M GPS Reb (SERIAL, BT), iX3M GPS Tech+ (SERIAL, BT), iX3M Pro Deep (SERIAL), iX3M Pro Easy (SERIAL), iX3M Pro Fancy (SERIAL), iX3M Pro Pro (SERIAL), iX3M Pro Reb (SERIAL), iX3M Pro Tech+ (SERIAL)"

"Scubapro: Aladin H Matrix (BLE), Aladin Sport Matrix (BLE), Aladin Square (USBHID), G2 (USBHID, BLE), G2 Console (USBHID, BLE), G2 HUD (USBHID, BLE)"

"Seac: Guru (SERIAL), Jack (SERIAL)"

"Seemann: XP5 (SERIAL)"

"Shearwater: Nerd (SERIAL, BT), Nerd 2 (BLE), Perdix (SERIAL, BT, BLE), Perdix AI (BLE), Petrel (SERIAL, BT), Petrel 2 (SERIAL, BT, BLE), Predator (SERIAL, BT), Teric (BLE)"

"Sherwood: Amphos (SERIAL), Amphos Air (SERIAL), Insight (SERIAL), Insight 2 (SERIAL), Vision (SERIAL), Wisdom (SERIAL), Wisdom 2 (SERIAL), Wisdom 3 (SERIAL)"

"Subgear: XP-Air (SERIAL)"

"Suunto: Cobra (SERIAL), Cobra 2 (SERIAL), Cobra 3 (SERIAL), D3 (SERIAL), D4 (SERIAL), D4f (SERIAL), D4i (SERIAL), D5 (USBHID, BLE), D6 (SERIAL), D6i (SERIAL), D9 (SERIAL), D9tx (SERIAL), DX (SERIAL), EON Core (USBHID, BLE), EON Steel (USBHID, BLE), Eon (SERIAL), Gekko (SERIAL), HelO2 (SERIAL), Mosquito (SERIAL), Solution (SERIAL), Solution Alpha (SERIAL), Solution Nitrox (SERIAL), Spyder (SERIAL), Stinger (SERIAL), Vyper (SERIAL), Vyper 2 (SERIAL), Vyper Air (SERIAL), Vyper Novo (SERIAL), Vytec (SERIAL), Zoop (SERIAL), Zoop Novo (SERIAL)"

"Tecdiving: DiveComputer.eu (SERIAL, BT)"

"Tusa: Element II (IQ-750) (SERIAL), Zen (IQ-900) (SERIAL), Zen Air (IQ-950) (SERIAL)"

"Uwatec: Aladin Air Twin (SERIAL), Aladin Air Z (SERIAL), Aladin Air Z Nitrox (SERIAL), Aladin Air Z O2 (SERIAL), Aladin Pro (SERIAL), Aladin Pro Ultra (SERIAL), Aladin Sport Plus (SERIAL), Memomouse (SERIAL)"

qqwindow screen has ldpi/pdpi 71.9691 149.144

qrc:/org/kde/kirigami/GlobalDrawer.qml:258: TypeError: Cannot read property 'length' of undefined

qrc:/org/kde/kirigami/GlobalDrawer.qml:293: TypeError: Cannot read property 'length' of undefined

qrc:/org/kde/kirigami/GlobalDrawer.qml:292: TypeError: Cannot read property 'length' of undefined

Window width changed to 796

Column width 796 root item width 796

width in Grid Units 41 original gridUnit 19 now 19

Window width changed to 411

Column width 411 root item width 411

width in Grid Units 21 original gridUnit 19 now 19

---------- finish ----------

To view this discussion on the web visit https://groups.google.com/d/msgid/subsurface-divelog/00FFF28B-4345-4644-87BF-B462B7C0E60F%40hohndel.org.

[Adric Norris]

Should've added that I'm using a Google Pixel 3 XL, running the Android 10 final release (QP1A.190711.020, Sep 2019).

--

"In the beginning the Universe was created. This has made a lot of people very angry and been widely regarded as a bad move." -Douglas Adams

[David Heim]

It also worked for me, thank you! I am using a Xiaomi Mi note 2 by the way.

Il giorno lunedì 23 settembre 2019 13:24:10 UTC+8, Dirk ha scritto:

It appears that a fix that solves a UI layout problem on a number of devices causes a regression on a small number of different devices. It's not quite clear to me how to make things work on all of them.

In most cases where this problem now appeared, turning your phone sideways, waiting for Subsurface-mobile to redraw its screen and then turning it into portrait mode again appears to be a workaround that get you the correct screen layout.

Please try this, and if it works, afterwards tap the menu, tap About, tap the button, copy the log files and send them to me.

Thanks

/D

On Sep 22, 2019, at 7:56 PM, Stuart Vernon <stu...@force2.net> wrote:

I am getting the same behavior. No way to access the main menu.

 

Also, I see other things that I think are issues:

 

• No dive # displayed next to the dives in the Dive list.
• When I tap a dive to open it it is displaying “wider” than my actual screen/display. For example, I cannot see the Map It button. But, if I swipe the dive slowly to the left the Map it button, dive #, and other things that are supposed to appear on the right side of the screen come into view. But, when I take my finger off the screen, the displayed dive either snaps back to the right or rolls further to the left, showing the next dive. Regardless, I do not have access to the Map It button and can only see things like the dive #, Water Temp, and SAC by pulling the dive over to the left and holding.
• If I scroll all the way to the bottom of the Dive List, the last dive is displayed with the system button bar covering half of it.

 

This is with Subsurface-mobile (Beta) Version 2.2.1 (4.9.3.30). Running on a Samsung Galaxy Note 8 running Android version 9.

 

From: Subsurface Group <subsurfac...@googlegroups.com> on behalf of David Heim <dhs...@gmail.com>
Reply-To: Subsurface Group <subsurfac...@googlegroups.com>
Date: Sunday, September 22, 2019 at 10:37 PM
To: Subsurface Group <subsurfac...@googlegroups.com>
Subject: No more menu button on Android app

 

Hi, I have been using the android app for a while and have not encountered problems so far.

But yesterday when I opened the app after some flickering the dive log page came up. However the main menu button does not appear anymore and therefore I cannot any other features of the app (see screenshot). 

 

Any fixes? 

Thank you

-- 
You received this message because you are subscribed to the Google Groups "Subsurface Divelog" group.

To unsubscribe from this group and stop receiving emails from it, send an email to subsurface-divelog+unsub...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/subsurface-divelog/14c74c2e-ee27-486b-a6f4-67e03e8676e7%40googlegroups.com.

-- 
You received this message because you are subscribed to the Google Groups "Subsurface Divelog" group.

To unsubscribe from this group and stop receiving emails from it, send an email to subsurface-divelog+unsub...@googlegroups.com.

[Darrell Barabash]

I'm running the same Google Pixel 3 XL device but Android 9 and I do not have this issue. UI seems to be working fine and I like the new fonts as my old eyes can read them now. Seems like this issue might be related to Android 10???

Not sure if this is helpful but thought I'd toss it out just in case. 

To view this discussion on the web visit https://groups.google.com/d/msgid/subsurface-divelog/CAJueESryAgxBQhu6XT4tmbEPM-%2BARNuVeFCpuC8bdGJKEhqhEg%40mail.gmail.com.

[Lars Dennert]

Even on the one plus phones it does this and I had discovered that rotating fixed it.

I'm going to guess that the mobile scaling is used incorrectly to initialize the viewport dimensions setting in the code for elements that shouldn't be scaled beyond the viewport size.

[Dirk Hohndel]

So this issue shows up with a variety of devices it seems, on both Android 9 and 10. I cannot figure out the pattern.
I have one device where it happens maybe one out of five times I start Subsurface-mobile.

What happens is roughly this.

When Subsurface first starts, it sometimes doesn't detect the screen width correctly. But then it gets a "screen width changed" notification with the correct width. And this is the underlying issue why I made the change that is now causing the problem in the first place.

But then, sometimes, on some devices, it gets several additional "screen width changed" notification quickly after each other, those with bogus information.
If you later rotate the device, we get two correct "screen width changed" notifications and all is well.

But why we sometimes get those additional, bogus ones right after the start? I have no idea.

/D

[Dirk Hohndel]

That's a reasonable assumption, but in my debugging attempts so far that doesn't seem to be the actual culprit.

/D

[Lars Dennert]

API 17 has display.getrealsize(size);
width=size.x

https://stackoverflow.com/questions/14341041/how-to-get-real-screen-height-and-width

Maybe a hack like that...

[Dirk Hohndel]

Correct - the challenge is that we really don't want to go around Qt to make sure we aren't missing any scaling factors that Qt sees.
But yes, I was thinking to use that value to get a better idea if things have actually changed or if we are getting false notification.
My guess is that this will be a bit of trial and error until I get it right :-(

[Stephen Smith]

Samsung 10+ running Android 9 has the same issue.

[Dirk Hohndel]

Did you have a chance to try the latest Beta that I pushed to Google Play (2.2.2)?

I am hoping that this will fix the issue

/D

--
You received this message because you are subscribed to the Google Groups "Subsurface Divelog" group.
To unsubscribe from this group and stop receiving emails from it, send an email to subsurface-dive...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/subsurface-divelog/80643e87-406f-4706-bd49-e57a58264cb8%40googlegroups.com.

[Stuart Vernon]

Still broken. 

---------- subsurface.log ----------

"0.024: Successfully opened logfile /storage/emulated/0/subsurface.log at Fri Sep 27 16:49:32 2019"

"0.024: Starting Subsurface-mobile:2.2.2(4.9.3.81):Android (9.0):arm64:en-US"

"0.024: built with libdivecomputer v0.7.0-devel-Subsurface-NG (ce6d9896a79afaa82641132e338f8744714c8593)"

"0.024: built with Qt Version 5.12.4, runtime from Qt Version 5.12.4"

"0.024: built with libgit2 0.26.0"

"0.025: Running on Android (9.0)"

"0.025: SM-N950U1/samsung/greatqlteue"

BTDiscoveryReDiscover: localBtDevice.isValid() true

"BTDiscoveryReDiscover: localDevice Stuart's Note8 is powered on, starting discovery"

paired BT classic device type 1 with address "00:00:00:00:B3:59"

paired BT classic device type 1 with address "10:00:E8:AD:BF:D8"

paired BT classic device type 1 with address "00:01:95:0F:66:B6"

paired BT classic device type 3 with address "24:DA:9B:1B:2E:9D"

paired BLE device type 3 with address "LE:24:DA:9B:1B:2E:9D"

paired BLE device type 2 with address "LE:E5:20:CB:C5:F7:35"

paired BT classic device type 1 with address "00:04:3E:50:CF:63"

paired BLE device type 2 with address "LE:C2:02:D6:CD:61:A8"

paired BT classic device type 1 with address "00:22:A0:A6:03:D0"

paired BT classic device type 1 with address "00:0A:9B:79:93:93"

paired BT classic device type 1 with address "00:0A:9B:79:93:92"

paired BT classic device type 1 with address "B8:BB:AF:C0:6A:26"

paired BLE device type 2 with address "LE:CC:78:AB:25:A5:48"

paired BT classic device type 1 with address "EC:65:CC:1B:54:C6"

paired BLE device type 2 with address "LE:E6:12:E3:A8:FE:60"

paired BT classic device type 1 with address "10:00:E8:6C:90:FF"

Found new device: "Rowkin Bit S-B" "00:00:00:00:B3:59"

Not recognized as dive computer

Found new device: "Predator" "10:00:E8:AD:BF:D8"

"this could be a Shearwater Predator"

Found new device: "Sena SMH10 v5.0.1" "00:01:95:0F:66:B6"

Not recognized as dive computer

Found new device: "Moto 360 29DL" "24:DA:9B:1B:2E:9D"

Not recognized as dive computer

Found new device: "Moto 360 29DL" "LE:24:DA:9B:1B:2E:9D"

Not recognized as dive computer

Found new device: "Teric" "LE:E5:20:CB:C5:F7:35"

"this could be a Shearwater Teric"

Found new device: "OBDLink MX+ 52473" "00:04:3E:50:CF:63"

Not recognized as dive computer

Found new device: "Perdix" "LE:C2:02:D6:CD:61:A8"

"this could be a Shearwater Perdix"

Found new device: "Uconnect" "00:22:A0:A6:03:D0"

Not recognized as dive computer

Found new device: "PB Stuart 1" "00:0A:9B:79:93:93"

Not recognized as dive computer

Found new device: "Stuart 2" "00:0A:9B:79:93:92"

Not recognized as dive computer

Found new device: "[Samsung] R5" "B8:BB:AF:C0:6A:26"

Not recognized as dive computer

Found new device: "Contour7830-1430274" "LE:CC:78:AB:25:A5:48"

Not recognized as dive computer

Found new device: "Uconnect" "EC:65:CC:1B:54:C6"

Not recognized as dive computer

Found new device: "Teric" "LE:E6:12:E3:A8:FE:60"

"this could be a Shearwater Teric"

Found new device: "Predator" "10:00:E8:6C:90:FF"

"this could be a Shearwater Predator"

Paired = "Rowkin Bit S-B" "00:00:00:00:B3:59"

Paired = "Predator" "10:00:E8:AD:BF:D8"

Paired = "Sena SMH10 v5.0.1" "00:01:95:0F:66:B6"

Paired = "Moto 360 29DL" "24:DA:9B:1B:2E:9D"

Paired = "Moto 360 29DL" "LE:24:DA:9B:1B:2E:9D"

Paired = "Teric" "LE:E5:20:CB:C5:F7:35"

Paired = "OBDLink MX+ 52473" "00:04:3E:50:CF:63"

Paired = "Perdix" "LE:C2:02:D6:CD:61:A8"

Paired = "Uconnect" "00:22:A0:A6:03:D0"

Paired = "PB Stuart 1" "00:0A:9B:79:93:93"

Paired = "Stuart 2" "00:0A:9B:79:93:92"

Paired = "[Samsung] R5" "B8:BB:AF:C0:6A:26"

Paired = "Contour7830-1430274" "LE:CC:78:AB:25:A5:48"

Paired = "Uconnect" "EC:65:CC:1B:54:C6"

Paired = "Teric" "LE:E6:12:E3:A8:FE:60"

Paired = "Predator" "10:00:E8:6C:90:FF"

"0.141: Created position source android"

"0.142: Set GPS service update interval to 300 s"

"0.162: location service is available"

qrc:/org/kde/kirigami/Page.qml:276:5: QML Loader: Binding loop detected for property "active"

Window width changed to 630

not recalculating base unit

Model size of -1 is less than 0

"0.741: Synchronising data file"

"0.766: Load dives from local cache"

"1.116: Successfully opened dive data"

"1.135: AppState changed to active with save ongoing and no unsaved changes"

"1.139: 364 dives loaded from cache"

"1.140: have cloud credentials, trying to connect"

"1.140: Have credentials, let's see if they are valid"

Completed connection with cloud storage backend, response "[OK]"

Window width changed to 411

first real change, so recalculating units

Column width 411 root item width 411

width in Grid Units 21 original gridUnit 21 now 19

Done setting up sizes

Window width changed to 570

not recalculating base unit

checkPendingIntents 

SubsufaceTheme constructor completed, initial width 570

Column width 570 root item width 570

width in Grid Units 30 original gridUnit 19 now 19

Done setting up sizes

Using the following font: Roboto at 15.380952380952381pt with mobile_scale: 1

qqwindow devicePixelRatio 3.5012 3.5012

qqwindow screen has ldpi/pdpi 71.9754 147.399

"3.240: Synchronising data file"

"3.259: Sync with cloud storage"

qrc:/org/kde/kirigami/GlobalDrawer.qml:258: TypeError: Cannot read property 'length' of undefined

qrc:/org/kde/kirigami/GlobalDrawer.qml:293: TypeError: Cannot read property 'length' of undefined

qrc:/org/kde/kirigami/GlobalDrawer.qml:292: TypeError: Cannot read property 'length' of undefined

"3.905: Successful cloud connection, fetch remote"

"4.736: Done syncing with cloud storage"

"4.741: Cloud sync shows local cache was current"

Window width changed to 797

not recalculating base unit

Window width changed to 411

not recalculating base unit

"15.400: AppState changed to inactive with no save ongoing and no unsaved changes"

"16.614: AppState changed to suspended with no save ongoing and no unsaved changes"

"18.059: AppState changed to active with no save ongoing and no unsaved changes"

---------- finish ----------

To view this discussion on the web visit https://groups.google.com/d/msgid/subsurface-divelog/D1E0B1FB-C2E8-40D4-B5E7-0122BC10A99D%40hohndel.org.

[Dirk Hohndel]

The log seems to indicate that we have the correct width both after start up and after rotating to landscape and back.
I'm seriously puzzled how this can show the wrong scale at startup but the right scale after rotating.
It's insulting to say "are you sure?", but on the flip side, I am quickly running out of ideas for this one...

From my phone

[Michael Raider]

I found the beta and was sun missing the menu too. I only tried portrait mode.

Sent from my Android phone.

[Dirk Hohndel]

Switching from portrait to landscape and back is a workaround.

But I am seriously stunned why we still see this behavior.

I think I need to go back to the last version that didn't exhibit this and figure out what triggered it in the first place.

/D

[Dirk Hohndel]

I finally found a device where I was able to reproduce the problem - I could have sworn that I had tried that one before, but I have quite a few Android devices by now so it's easy to lose track...
Anyway, I was able to fix the issue and then validated that I get the correct screen size (with and without rotating) on seven different devices ranging from a tiny Sony phone on Android 6 to a Pixel 3 XL and a OnePlus 6.
I pushed a new beta which should show up as a new update on Google Play shortly. 2.2.2 (4.9.3.106)
This one also fixes the bugs around dive downloading that have marred the current production version as well as the last few betas.

I'm hoping that we are close to something that closes these two weeks of non-stop problems on Android...

Thanks for everyone's patience. As always, I'm very interested in feedback on that latest version.

While I wait for Google Play to actually push this out I'll clean up the patches and make them available for review...

/D

[Lars Dennert]

I can verify that it is fixed on the one plus 7 pro. Sorry I couldn't be more help and look at the code as well

[Michael Raider]

It's corrected on my galaxy S7 too.

On September 29, 2019 1:22:26 AM UTC, Lars Dennert <larsd...@gmail.com> wrote:

I can verify that it is fixed on the one plus 7 pro. Sorry I couldn't be more help and look at the code as well

[Dirk Hohndel]

Excellent - I really appreciate people reporting back as that gives me confidence that this is seeing enough testing.

/D

[Paul Buxton]

Works for me, but I hadn't seen issues before..

--
You received this message because you are subscribed to the Google Groups "Subsurface Divelog" group.
To unsubscribe from this group and stop receiving emails from it, send an email to subsurface-dive...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/subsurface-divelog/20F54B97-5FC0-43C2-9F75-BDA865155EEF%40hohndel.org.

[Adric Norris]

Sorry for the delay, but I can confirm this is working as expected on my Pixel 3 XL running Android 10.

--
You received this message because you are subscribed to the Google Groups "Subsurface Divelog" group.
To unsubscribe from this group and stop receiving emails from it, send an email to subsurface-dive...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/subsurface-divelog/0052B847-BFDB-4B6D-A0C5-FAE0B08C86A8%40hohndel.org.