@Voorstad i plan on three in one actually im developing a custom firmware will feature meshnet but also have compatibility with meshtastic and meshcore protocols as well ...the goal when im done in a brand new esp32 s3 /p4 firmware thats is the most advanced and feature complete ....however im hitting alot of bumps in the road ....and money! ...each prototype modem estimated cost will be around $520 ....once i bang out a prototype i wanna raise money to mass produce sbc's for it hopefully bring the cost down to $100 per modem .......i currently work at burger king ...so this is a financial nightmare moving at a snails pace ..unfortunately ...but yeah will be apps within the firmware

@gpatel-fr Right, thanks!

@YamiYukiSenpai all Merge Requests are very welcome

@arubislander i think iv also decided to use UT at the main mobile interface for all my esp32 related projects so alot of tools are in the works ....will be very much a industrial microcontroller programming tool when im done

New version is out. Changes: Reduce application size by combining LTO and static linking Remove limit on processed memory size Fix Spanish model installer Change label text for installed models

About the state of Frameworks and Game Engines: Unity: There is a Demo App in the store that prints FPS. Godot: There is also a kind of benchmark-like Demo App. Bacon2D: works, but is unmaintained for 8 years now. I believe that anything based on SDL or WebGL (or Qt) should do. Providing SDL3 with better system integration is in the works. Clickable provides a Godot app template, but this is for UT 20.04 currently. 24.04 support probably comes after beforementioned SDL3 (+SDL2 via compat layer) support is finished.

@Talkless sorry to hear that and that the debugging was such a painful process. Let me know if you have ideas for improvements or decide to get back to this issue.

@projectmoon yeah, it is proprietary

@Keneda missed that thanks, @googlybear well still nothing I can do about it directly. though I am implementing the xdg-desktop-portal standard into lomiri atm, so this may indirectly help you because there are a bunch of xdg bitwarden apps.

It seems Droidian have their own modified version of Firefox with some UI adaptation: https://github.com/droidian/firefox-esr-mobile-config

@ikoz Nice but only works in QML, for example I can't use that in Signal UT. It might be ok for Kaidan though! Is it possible to fetch the keyboard normal height for the device in terminal?

This does not happen when streaming over bluetooth.

@lduboeuf well done ! it works !

@pparent I have installed VLC in Waydroid and it works great so a native app would be awesome.

This is SO HARD and I absolutely love it. Thank you again for another great app!

@spacenerdmo Thanks a lot! I'm gonna test it and let you know how it's going

@kugiigi said in [Question] getprop in a confined app?: based on physical measurement I think that this physicalDotsPerInch thingy could be affected by the idea that QT has about the physical size of the screen: using my first pyqt application: from PyQt5.QtWidgets import QApplication q=QApplication(['demo']) ls = q.screens() myscr=ls[0] print(f"name={myscr.name()}") print(f"logicalDotsPerInchX={myscr.logicalDotsPerInchX()}") print(f"logicalDotsPerInchY={myscr.logicalDotsPerInchY()}") print(f"physicalDotsPerInch={myscr.physicalDotsPerInch()}") print(f"physicalDotsPerInchX={myscr.physicalDotsPerInchX()}") print(f"physicalDotsPerInchY={myscr.physicalDotsPerInchY()}") print(f"physicalSize={myscr.physicalSize()}") print(f"size={myscr.size()}") print(f"devicePixelRatio={myscr.devicePixelRatio()}") print(f"depth={myscr.depth()}") print(f"virtualSize={myscr.virtualSize()}") print(f"geometry={myscr.geometry()}") I get: name=XWAYLAND0 logicalDotsPerInchX=96.25263157894736 logicalDotsPerInchY=96.05042016806723 physicalDotsPerInch=320.48931496290584 physicalDotsPerInchX=320.51134020618554 physicalDotsPerInchY=320.46728971962614 physicalSize=PyQt5.QtCore.QSizeF(97.0, 214.0) size=PyQt5.QtCore.QSize(1224, 2700) devicePixelRatio=1.0 depth=24 virtualSize=PyQt5.QtCore.QSize(1224, 2700) geometry=PyQt5.QtCore.QRect(0, 0, 1224, 2700) since for my FP5, the physical size of the screen is supposed to be 21.4cm, that is, 8.425 inches, this gives 2700/(21.4/2.54) = 320.4672897196262 and that's physicalDotsPerInch is reporting in my test with pyqt on my FP5. Maybe Volle phones are also misreporting the physical size of the screen ? Edit: I think I understand; I am using straight qt and pyqt that has no knowledge of mir, that's why it is using xcb: printenv returns QT_QPA_PLATFORM=ubuntumirclient;wayland-egl;ecb I'll search if there is a way to get a plugin to enable my pyqt for ubuntu touch maybe it could give better results. Edit 2: not found but I now doubt that there is a good way to fix it on the FP5, Internet gave me the useful tip to use an utility called 'mirout', and it reports to me: phablet@ubuntu-phablet:~$ mirout Connected to server: <default> Output 1: LVDS, connected, 1224x2700+0+0, enabled, on, 97mm x 214mm (9.3"), normal, 3.00x, unknown, phone 1224x2700 60.00*+ Output 2: DisplayPort, disconnected Output 3: Virtual, disconnected 1920x1080 60.00*+ so the problem is indeed with the phone, not the driver.