OverviewFelgo 2 Support (Qt 5) › AppMap broken on Android: Scaling does not work, fonts are not readable

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
  • #22897


    Hi FELGO folks,

    Unfortunately, the AppMap is still basically broken on Android (look here for our previous report). Just try out your own Maps Demo or even just look at your own screenshots for it: The scaling is broken, the fonts are not readable.

    With FELGO’s own scaling system in place, your advice is not to use

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

    — and if one does anyway, the navigation bar has a twice its height on many Android devices. The solution to use manual scaling as suggested here does not work (see link).

    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?

    Do you have any suggestions?




    Felgo Team

    Hi Micu,

    what map provider are you using? Here is a potential fix that you can try:


    QApplication::setAttribute(Qt::AA_EnableHighDpiScaling); // Add this as first line of the main function


    import Felgo 3.0
    import QtQuick.Window 2.12
    App {
      onInitTheme: {
        // this hotfixes a faulty status bar height size after enabling the default Qt high dpi support in main.cpp
        Theme.statusBarHeight = Theme.statusBarHeight/Screen.devicePixelRatio
      // ...

    Let me know if this fixes the map scaling, and if your remaining app UI works as expected. We could then go ahead and try to apply a similar solution within the engine itself.




    Hi Alex,

    thanks a lot for your answer! <3

    Unfortunately, this workaround doesn’t work šŸ™

    TypeError: Cannot assign to read-only property "statusBarHeight"

    (Now I actually remember I have tried this already myself).





    BTW: What is the difference between

    QApplication::setAttribute(Qt::AA_EnableHighDpiScaling); // Add this as first line of the main function


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

    on Android?


    what map provider are you using?

    MapBox…. but as Julian wrote in hisĀ  previous post, this issue is independent of the map provider.







    Addendum: I tried sth. else

    Theme.navigationBar.height = Theme.navigationBar.height/Screen.devicePixelRatio

    This does not lead to a syntax error, it also makes the bar have the right height. BUT: The icons left and right of the navigation bar (back button e.g.) are shifted half of the bar height down now šŸ™




    Honestly, this is getting really frustrating. And kind of a deal-breaker. In the picture below you can see on the left how it looks like without autoscaling and on the right with the following patch:

    navigationBar.anchors.topMargin: -navigationBar.height / 2.5;

    The factor is obviously hard-coded, so I doubt this will work across different devices. I haven’t found out which variable is set incorrectly in Felgo, so I cannot workaround it.





    @alex here is the workaround we came up with incl. some values for navigationBar.height and Theme.statusBarHeight:

    NavigationStack {
        Component.onCompleted: {
            // This hotfixes a faulty navigation bar height on Android after enabling the default Qt high dpi support in main.cpp:
            if (!BVApp.Platform.isAndroid) {
            // Before the next line "navigationBar.height = 139.97597452201887" on my test device.
            anchors.topMargin = 1
            // The line above triggers something so that the "navigationBar.height = 55.97597452201887", but now it is partly hidden
            // by the status bar on Android, so we add "Theme.statusBarHeight" but taking the high dpi scaling factor into account.
            navigationBar.height += Theme.statusBarHeight / Screen.devicePixelRatio
            // Afterwards the "navigationBar.height = 79.96567788859839". Next we reset the anchor again to its default value.
            anchors.topMargin = 0
            // As comparison: without high dpi "navigationBar.height = 56" and "Theme.statusBarHeight = 24" on my test device.

    For me the weirdest part is that changing topMargin changes theĀ navigationBar.height.

    Best regards,


Viewing 6 posts - 1 through 6 (of 6 total)

RSS feed for this thread

You must be logged in to reply to this topic.

Voted #1 for:

  • Easiest to learn
  • Most time saving
  • Best support

Develop Cross-Platform Apps and Games 50% Faster!

  • Voted the best supported, most time-saving and easiest to learn cross-platform development tool
  • Based on the Qt framework, with native performance and appearance on all platforms including iOS and Android
  • Offers a variety of plugins to monetize, analyze and engage users
create apps
create games
cross platform
native performance
3rd party services
game network
level editor
easiest to learn
biggest time saving
best support