@alaskalinuxuser said in Call for testing - Kaidan 0.6.0 for Focal/Noble.: Good news! Awesome! ^__^ In landscape mode the list of contacts scrolls and you can select ones from the bottom. It works! The keyboard height is now figured mathmatically, so it should scale for everyone and work/look proper. Well done! In landscape or portrait mode, the search bar is now wider and usable. It is wider, indeed. It has some overlap though Nothing terrible If you swipe up or down a conversation, the ListView will go over the top Search or the bottom TextArea [image: 1765661754221-83958ec8-c906-4235-8292-be81a469bf28-imatge.png] [image: 1765661735185-f3011fc4-cafb-4f44-be22-63905281d541-imatge.png]

Merezhyvo version 0.4.4 has been released. Here are the main changes: Third-party cookies control New global setting to block or allow third-party cookies. You can now add per-site exceptions when a site breaks without them (for example: some logins, widgets, or embedded content). These exceptions are visible both on the internal “Manage security exceptions” page and in the shield popover for the current site. New “Site data” page New internal page where you can inspect and clear cookies and stored data per site. There is also a “Clear all data” button if you want a full reset. Some entries in this list may be from domains you did not visit directly (for example CDNs, analytics, embedded content); that’s normal, and now it’s easier to see and clean them. “Privacy & Security – How this works” New internal help page that explains, in simple terms, how HTTPS, certificates, cookies, WebRTC and the internal tools behave in Merezhyvo. The goal is that you don’t need to be a security expert to understand what these options do. Better touch support Fixed drag/rotation gestures on some interactive sites that use custom canvas / SVG / D3 handling – for example earth.nullschool.net now works correctly on Ubuntu Touch. UI & translations The shield popover now also reflects non-default privacy/security settings (like cookie exceptions). Added Dutch, Spanish and Italian translations. Improved layout, added Close buttons on internal security pages, and fixed some issues with accent letters on the on-screen keyboard. As always, feedback is very welcome – especially if you notice any regressions with the new privacy tools or interactive sites.

I eventually figured out how to get the 'Sealed' app working, by changing the URL from bitwarden.com (the default) to https://vault.bitwarden.eu. bitwarden.eu does not work!

Thanks for the feedback, I will keep improving this tool

This does not happen when streaming over bluetooth.

@lduboeuf well done ! it works !

@pparent very cool

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

https://github.com/orgs/organicmaps/discussions/11805

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

Thank you for the donation!

@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.