@Inali
Thank you for the effort, maybe this site helped a little bit. The solution i've found is a simple: sudo ufw allow out on waydroid0 to any. I was (and still am) confused about the 2 devices and how they "work" together. Now that i know which interface to deal with i can, of course, precise this rule, but i have another (Android-) firewall in the waydroid container that can handle this.

Hello all,

when i connect bluetooth mouse & keyboard to my Fairphone 4, connect the phone to my TV with a USB-C-to-HDMI-cable and start Waydroid, Waydroid starts correctly, but crashes and restarts as soon as i hover with the mouse cursor over the Waydroid window. There aren't any useful informations when starting Waydroid from Terminal, even with --verbose and/or --details-to-stdout enabled.

Anyone has an idea what the problem is?

Hello all,

i've installed an app that warns me e.g. in the case of fire. It was removed from the OpenStore, but it's source code can be found here: https://github.com/S60W79/warnapp-deutschland or https://gitlab.com/S60W79/warnapp-deutschland.

The problem is i've activated ufw and because of that i don't receive the push notifications.

Does anyone know which port to open for this or a way to find out which port is used or which firewall rule to set?

Thanks all!

@kugiigi When using QGuiApplication::setAttribute(Qt::AA_EnableHighDpiScaling); it looks the same on phone and TV. That's nice, but i think i will stick with units.gu(). I've tried it and, so far, it works nice. I saw there are problems, but that's not the fault of my app.

@wynn1212 You're the best . TBH i was hoping you would do it, because you faced the same problem. Maybe there will be a real solution soon .

@ikoz I use the Label component somewhere else in the app and the scaling problem persists. The text is still very large on TV.

@kugiigi I've used units.gu() before, but didn't know or forgot the meaning of it. This maybe a good hint, i will try this. Thank you.

As for the header i've found another solution:

Set font.pointSize to hdrrec.height/3, this way the relation stays the same. Maybe i will use this relation thing for other texts the problem still persists, because Text components for which I didn't set a size has no scaling problem. E.g. setting font.pointSize to txt1.font.pointSize*2 or i will try with the grid units like mentioned above.

I will write again in the event of further problems.

@kugiigi I think i've logged into gitlab via my github account. Why shouldn't this be simply possible in the future? Maybe you're right, i don't know. Another reason for me to remove the account was that i have so many accounts on the internet and don't want to lose overview. Perhaps I will try to open one again.

@wynn1212 Sorry, but i have no gitlab account. I had one, but removed it because i haven't used it for quite a while.

Hello all,

i'm working on an app that, so far, works well on phone screen. But when connecting the phone to a TV over USB-C-to-HDMI-cable e.g. the PageHeader text is extremely large. Here's a sample code:

Rectangle {
    id: mainPage
    anchors.fill: parent

    PageHeader {
        id: header
        title: "ABC"
        z: 1
        contents: Rectangle {
            id: hdrrec
            anchors.fill: parent
            color: "white"
            Text {
                id: hdrtxt
                anchors.left: hdrrec.left
                anchors.verticalCenter: hdrrec.verticalCenter
                text: header.title
                font.pointSize: 40
            }

If i change font.pointSize to font.pixelSize the text is much smaller on phone screen but not on TV, it's still very large, i can't even see a difference between font.pointSize and font.pixelSize.

Does anyone know what i should change or which Text QML Type properties to use? I can't find any useful informations from Google. I guess it's a special Ubuntu Touch thing, because of the possibility to change between windowed and staged mode?

This is not the only problem, maybe someone can help me with the others, too.

Edit: I have found Screen QML Type, is this the way to go?

Ok, i have tried for myself and downgraded the images. Waydroid doesn't crash anymore. This isn't really a solution, but fixes the problem for now. Thank you very much.

Btw. with the newer images Avast finds malware in htmlviewer. Maybe this is false positive, i don't know. This is no problem with the old 20250426 image, cause htmlviewer isn't even installed.

@wynn1212 : Show taps is disabled in my Developer options. When enabling it, Waydroid and eventually whole Lomiri crashes. After that even touch inputs (without external display) don't work anymore, Waydroid instantly crashes. To disable it again (i'm glad this was possible, cause Waydroid remains unusable with Show taps enabled) i had to do a adb shell settings put system show_touches 0 in Terminal. When using a bluetooth mouse without external display Waydroid crashes, too.

Is it possible to downgrade Lineage images without data loss? I can try if this fixes the problem for now.

Hello all,

when i connect bluetooth mouse & keyboard to my Fairphone 4, connect the phone to my TV with a USB-C-to-HDMI-cable and start Waydroid, Waydroid starts correctly, but crashes and restarts as soon as i hover with the mouse cursor over the Waydroid window. There aren't any useful informations when starting Waydroid from Terminal, even with --verbose and/or --details-to-stdout enabled.

Anyone has an idea what the problem is?