@AppLee No not yet Marius was working on it.

@bamboy360 said in Aplications from Google Store.: UT's "guided" way of installing waydroid can let you access some GooglePlay apps via AuroraStore apk (a redistributor) without google services. In my experience however, this leads to some android apps needing those services, crashing and causing other problems with Waydroid. It's fiddly. If WayDroid is used without GAPP module, it's recommended to install the MicroG services (a fake Google services library). This will allow "most" apps that need Google services to run properly in WayDroid. The installation is simple and is described here: https://forums.ubports.com/topic/5907/open-ubuntu-touch-to-all-android-applications/115

I still can’t get wifi/bluetooth, even after using the Lenovo Software Fix tool to reset to android (where wifi/bluetooth work well on it) and started the installation again from the beginning. I still have the last image of UT flashed and followed the instructions well. (+ and the command fastboot format:ext4 userdata works correctly now, no need to format through the tablet) Maybe I should try to reinstall with ubports (hoping not to back again into the bootloop problem) or use another image ? (Maybe for some unknown reason, this image is problematic for me ?)

@Keneda Thanks, I'll need it

TL;DR: use BTRFS or proxy the ZFS via NFS @RJDan said in zfs on Ubuntu touch: [...] better supported on linux, it seemed to be a clear win for zfs. Well, unfortunately that is not the case, ZFS is not supported without adding kernel modules via DKMS. That is because of licensing issues which prevent it from being built-in the kernel like BTRFS and EXT4. DKMS cannot work on Halium kernels as they are based on patched downstream android kernel. I thought FUSE was an option, but after trying to install it on my device I found out zfs-fuse is deprecated, and I couldn't make it work. So the only way is to build the kernel with patches for the ZFS module, beforehand. This is however very complex and I wouldn't recommend it. There is a workaround, to have a NFS/Samba as a proxy to the ZFS file system so that the UT device accesses the file system remotely. The more straight-forward approach is to change the file system to BTRFS, assuming it meets your use cases. If you only need snapshots and backups, you should be fine.

@Moem Sorry, yes my translator didn't find laggy.. : but yes, indeed laggy : choppy, jerky... I edited above.

@Martin5 Yes, Marius already got it to work although only via CLI. You might be able to compile it yourself. It's something that's also used in other Linux distro. I haven't tried it myself though because I'm lazy and the issue doesn't bother me enought yet

Hello I can confirm ( I use airplane mode to redirect calls to another phone number ) After setting the mode the airplane switches after 1 or several rings ( i.e. it does not switch immediately after setting the airplane ... but after some activity )

@Keneda I just get know.

@Luksus Ah, thank you for explaining. So, as I understand it, there is work to be done before the Op5(t) can be moved forwards to Noble.

@haagch said in Volla Quintus Update fails: I guess I'll mark this as solved even though going through RC is more of a workaround than an actual solution, because the update really should just work. Hi @haagch , This is the way to go. The forum is not a bug tracker. You had an issue someone helped you solve it. For reporting bugs it should be done in the Gitlab or Github dedicated to the proper project. Can be Ubuntu Touch, a specific app, a device specific issue, ...

@domubpkm I use mpv in libertine and it works really good.

@ikoz Hi, Thanks for the reply... Unfortunately , test_gps doesn't work at all ("**** GPS interface not found Bye!*" ), tried that yesterday, no wrapping around it would give anything... looks like that comes from the hybris stack for old android stuff that accessed GPS hardware directly... Since I believe the hardware to be already locked/in use by the the software stack, I probably need to simulate the same approach (Qt > QtPosition or Dbus sessions ?) I'll try working with QtPositioning somehow since GPSToolkit uses it USB: yeah, i'll check again later, ideally, I just need a way to inject juice and have a single usb, dunno Network: Yeah, honestly, if it can be Hotspot AP + Station at the same time, all done in UI to keep my dirty fingers away of the network management, that'd be great, or even by splitting the radio chains, 2.4GHs AP, 5GHz Client if needed I know the hardware can do it (because It did work before installing UBt) But it's less of an emergency

@lduboeuf Thanks for the answer Lionel. Well, i have made some tries but without success. Finally, i have remove the pip3 install of 8.3.1 and reinstall with snap and now it's working. There was something wrong with the blob fdc55cec6c2e

@alan_g yeah but i didnt mess with it, i just downloaded.

@walidham i fixed it by adding lineageos libcurl and then adding the path to build/core/main.mk thanks tho!

@Eric-H said in Resurrection of Indicator Upower: I can see POWER_SUPPLY_CHARGE_TYPE=Fast in udev battery info, so it seems to be a fast charge. No, I got Fast with low-end 7W charger too. My guess it's POWER_SUPPLY_FASTCHARGE_MODE=1. My device has POWER_SUPPLY_HI_POWER. How much power can your charger deliver? POWER_SUPPLY_POWER_NOW=39764516 looks realistic for 45W. I also tried to find the Fast Charging voltage (9..12V) on BMS and failed, so you can try it too. Probably not being monitored by software. And all of this is very device-specific.

@arubislander Yes.

@wynn1212 Thank you for your detailed reply. I was using Ubuntu 24.04.2 with Kernel Linux 6.8.0-57-generic both on and old AMD desktop first then on a Windows Surface Laptop (running same Ubuntu version) with a USB2.0 to USB C cable. Next I tried a USB C to USB C cable on a Dell laptop (also running latest Ubuntu version) and after 2 or so attempts the flash was successful (not clear why). However today, I did the same procedure with another new FP4 using the Dell Laptop and USBCtoC cable and it again failed initially. When I connected the phone (already in fastboot mode) and restarted the bootloader from fastboot when installer was asking to manually switch the phone to fastboot, I was successful. This is quite frustrating because it still is not clear to me how to exactly reproduce this issue. It is definitely not the cable or the computer used. I agree this must be an interaction between the Ubuntu version and/or kernel and the phone. It almost looks like a timing issue, restarting bootloader at the right time lets the process go through. I could not test on Windows because I only have a work laptop running windows which does not allow starting non-certified appimages.