[Julian]

Hello,

I have the issue (Felgo 2.16.1 – 2.18.2), that on Android all text (like street names, etc.) in a map are very small.

I figured out that, if I set:

<meta-data android:name="android.app.auto_screen_scale_factor" android:value="true"/>

In AndroidManifest.xml the scaling of the text is correct, unfortunately the NavigationBar is now double the size it should be.

Does anybody has the same issue? I wonder, how no one saw that.

Best,

Julian

[Julian]

auto_screen_scale_factor: false

https://www.dropbox.com/s/05jn9y04mzcc5fj/Screenshot_1544276774.png?dl=0

https://www.dropbox.com/s/10xhhf1b3s3a2w8/Screenshot_1544276780.png?dl=0

https://www.dropbox.com/s/qqqwabbxc8i82yd/Screenshot_1544276809.png?dl=0

auto_screen_scale_factor: true

https://www.dropbox.com/s/n5v5quhbsuq0dis/Screenshot_1544276635.png?dl=0

https://www.dropbox.com/s/6gvv3plrtmt4s3k/Screenshot_1544276648.png?dl=0

[Julian]

Any news here?

[GüntherFelgo Team]

Hi Julian,

you do not require the

<meta-data android:name="android.app.auto_screen_scale_factor" android:value="true"/>

setting in AndroidManifest, as this can lead to wrong scaling as seen with the NavigationBar.

 

About the Map issue:

• Which device(s) are you using for testing and what is their Android OS version?
• Which map provider are you using for the map?

Note: The MapBox provider also allows a highdpi_tiles setting, are you using this setting?

AppMap {
        id: map
        anchors.fill: parent

        plugin: Plugin {
          name: "mapbox"
          // configure your own map_id and access_token here
          parameters: [  PluginParameter {
              name: "mapbox.mapping.map_id"
              value: "mapbox.streets"
            },
            PluginParameter {
              name: "mapbox.access_token"
              value: "pk.eyJ1IjoiZ3R2cGxheSIsImEiOiJjaWZ0Y2pkM2cwMXZqdWVsenJhcGZ3ZDl5In0.6xMVtyc0CkYNYup76iMVNQ"
            },
            PluginParameter {
              name: "mapbox.mapping.highdpi_tiles"
              value: true
            }]
        }
}

Best,
Günther

 

 

[Julian]

Hey Günther,

thanks for your reply. I tried osm, mapbox, and mapboxgl. All with the same result. To show the issue even better I just took the Felgo Showcase app, run it as Desktop application, where everything is fine:

https://www.dropbox.com/s/y06brgi61a37yhj/Screen%20Shot%202018-12-17%20at%2019.15.26.png?dl=0

And ran it in Android emulator, where the text is super small:

https://www.dropbox.com/s/q0k844920zjy398/Screen%20Shot%202018-12-17%20at%2019.23.35.png?dl=0

Here are some details about my env if it helps:

macOS 10.13.6

NDK: android-ndk-16b

SDK: Android build platform: android-27

Emulator: Pixel_2_XL_API_27 (ABI: x86, Target: Android 8.1 (Google APIs))

This also happens on a Huawei P20 Pro.

Can you reproduce it with the Showcase app?

Best regards,

Julian

[GüntherFelgo Team]

Hi Julian,
thanks for the follow-up!

I am able to reproduce the problem – I’ve added the issue to our bug-tracker for further investigation.

As a workaround, you can apply additional scaling based on the screen density on Android like this:

      AppMap {
        id: map
        anchors.fill: parent

        // fix map scaling on android
        scale: Theme.isAndroid ? dp(1) : 1

        
        plugin: Plugin {
          name: "mapbox"
          // configure your own map_id and access_token here
          parameters: [  PluginParameter {
              name: "mapbox.mapping.map_id"
              value: "mapbox.streets"
            },
            PluginParameter {
              name: "mapbox.access_token"
              value: "pk.eyJ1IjoiZ3R2cGxheSIsImEiOiJjaWZ0Y2pkM2cwMXZqdWVsenJhcGZ3ZDl5In0.6xMVtyc0CkYNYup76iMVNQ"
            },
            PluginParameter {
              name: "mapbox.mapping.highdpi_tiles"
              value: true
            }]
        }
}

Note: The scale setting on AppMap also applies to e.g. custom MapQuickItem objects you place on the map. To not scale them along with the actual map, you can reverse the scale for these items:

MapQuickItem {
            // reverse scale for correct sizing
            scale: 1 / map.scale

           // other configurations
}

Best,
Günther from Felgo

[Julian]

Hey Günther,

thanks for you reply. That indeed worked around the problem. Just for future readers, instead of using anchors.fill: parent I had to apply some math:

-        anchors.fill: parent
+
+        // reverse scale for correct sizing
+        anchors.bottom: parent.bottom
+        anchors.left: parent.left
+        anchors.bottomMargin: (page.height - (page.height / map.scale)) / 2.0
+        anchors.leftMargin: (page.width - (page.width / map.scale)) / 2.0
+        width: page.width / map.scale
+        height: page.height / map.scale

 

Otherwise the map is over- or underflowing the parent.

 

Best,

Julian

[Micu]

Any news for this bug?

[Micu]

i am still a bit puzzled how to deal with our issue https://github.com/micuintus/harbour-Berlin-Vegan/issues/286

Could you give us some advice, please?

[AlexFelgo Team]

Hi Micu,

does applying a manual scale to the map on Android not work for you?

Cheers,
Alex

[Micu]

Hi Alex,

Thanks for your answer!

 

does applying a manual scale to the map on Android not work for you

Not really, unfortunately. Well, if I choose the solution suggested above, it does make the fonts have the right size on Android.

But

a) the gestures on the maps are clunky then (pinch and zoom, panning etc.),

b) the upscaling is pixel based, i.e. the map looks pixelated,

c) and, after all, this solution is a hack.

If I use auto_screen_scale_factor everything works perfectly — except for the issue mentioned by Julian of the navigation bar having twice its height then (on some devices, not on all though BTW).

Is there a way to fix the navigation bar size issue?

Or is there another way to mitigate the font size issue?

 

Any help would be highly appreciated.

Cheers,

micu

[Micu]

Hi folks,

Still no news on that front?

If I try out the FELGO demo applications using maps and if I look at the attached screenshots https://felgo.com/doc/felgo-appdemos-maps-example/, it seems to me that the problem is not just local to our app, but present in every FELGO application.

With FELGO apparently wanting to become the goto Qt for mobile solution, and maps being a pivotal feature for mobile applications, I am a bit perplexed that this issue does not take a higher priority, as it renders the map more or less unusable on Android.

[Micu]

FYI: Thanks to Julian’s workaround, finally Berlin-Vegan 3.6 could be released last month with a fixed map version:

https://github.com/micuintus/harbour-Berlin-Vegan/releases/tag/3.6

 

This is the WO by Julian:

https://github.com/micuintus/harbour-Berlin-Vegan/commit/184eb9638b1b967f748ce5656ad0a169c615da6

@alex: Doesn’t it make sense to fix this issue within FELGO itself?