@iceman198 https://t.me/oneplusnordn10UbuntuTouch is the group for this. I think its a matter of patience, the porter is heavily working on it.

@pparent Agreed, and i will follow your attempt closely

@pparent video script of bulletpoints on android to UT transition.

@pparent after a week of testing, the battery usage looks normal.

@bhdouglass Ok thank's a lot it worked! https://open-store.io/app/touchpiano.pparent I promise I will use Qt6/Qml6 very sparingly, until the library is available inside the OS. In the mean time this app can serve as a demonstration Qml6 app. Ps: But what might be usefull is to start building a a Qt6 version of Whatsweb, that is currently broken.

@nbdynl Apps like Signal or Whatsapp will maintain a background network connection with their servers weather or not they are calling. On top of they, if they wanted to spy on on you they could leverage that to start a fake invisible call/connexion, so that they can keep spying quietly when the phone is suspended. I don't think whether or not there is "an active forground connection", can be used to determine reliably if the app is legitimate to record the microphone when the screen is off...

I've put the logo on the french version of wikipedia, It can be reused for other languages: https://fr.wikipedia.org/wiki/Ubuntu_Touch

I've published the new revision (0.1.8) with the following improvements: -Fix layout problem coming from changes upstream -Improve ContentHub handling -Improve call icons layout I should also not crash on 24.04-2.x, although it will probably not be usable yet, as for now it seems that On-Screen-Keyboard does not work on any XWayland app. I will try to investigate more about that soon. I next revision I will try to add an option to configure scaling with fine grain, and few improvements/fixes in the UI.

Calls are available in this new app: https://open-store.io/app/whatslectron.pparent

@pparent did you notice that there are menus that are displaying fine in the ChromiumUT app ? the menus in the top bar are not working, but the Google application menu is working correctly (although there is a wobble the first time, maybe it's the automatic resizing you are referring to, but it's failing to stop it to work)

@projectmoon Can you do journactl -r | grep 99captive_portal ?

@pparent Sorry YES, corrected Running without your script. In fact, the network quite frequently disconnects and then reconnects but not instantly, often with a lag of a few seconds. That said, I am wary that this does not come from atmospheric conditions with high heat and azure blue skies where waves often circulate poorly.

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

@Moem I second this, I've been wondering why this was on recent in the inTouch app for who knows how long.

@Fuseteam I have tried to use crackle and have a few observations about it, do you prefer that I do it here (where it's a bit off-topic) or is there a better place where I should create a new topic ?

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

@CiberSheep said in [Question] Clickable: install target arch dependencies.: @pparent check here: https://clickable-ut.dev/en/latest/project-config.html You'll gonna love it Specially on dependencies_host and dependencies_target but there's a lot of thing to play with Ho that's great! It helps a lot thank's so much!

It does work better in 24.04-1.1 that it did in 24.04-1.0. I'm using google maps app from @chromiumos-guy If I open the app outdoor when I have access to my location it will usually work. BUT it will freeez/crash very easilly if I try to access the position when I don't have access to it (indoor) or that I click a second time on the position icon. Once it has crashed or freezed it will not work anymore until I reboot the phone.

For what it's worth, this bug should be solved in 24.04-1.3 (no need to apply a patch script: the sense that the placeholder does not remain open in background anymore). It could still be a nice fix to avoid that it uses a lot of CPU in the first place, as it could possibly allow for faster starts of the apps.

@Ida_ Thank you very much! Unfortunately, at the moment, this does not help me understand what happens on 24.04-2.x