using bind mounts in UT works on my FP4/OTA-1 (focal) without touching any permission settings etc as described in the waydroid documentation:

https://docs.waydro.id/faq/setting-up-a-shared-folder

for example:

 sudo mount --bind ~/Documents ~/.local/share/waydroid/data/media/0/Documents 
 sudo mount --bind ~/Downloads ~/.local/share/waydroid/data/media/0/Download 
 sudo mount --bind ~/Music ~/.local/share/waydroid/data/media/0/Music 
 sudo mount --bind ~/Pictures ~/.local/share/waydroid/data/media/0/Pictures 
 sudo mount --bind ~/Videos ~/.local/share/waydroid/data/media/0/Movies

allows sharing files in those directories between UT and waydroid both ways.

The one missing feature is making the bind mounts permanent. I added them to /etc/fstab but changes to that file don't seem to survive a reboot.

edit: I realize you did link to this and mentioned it doesn't work on xenial, I still posted here to let people know it can work on focal

Hi All
I played around with waydroid and my Bluetooth headphones on my FP4 (OTA-1). At some point the music app stopped working. I tried reinstalling it through the openstore and manually through the terminal. In the openstore I click on install, it runs the progress bar, and then simply returns to showing the install button. Downloading and manually installing shows this:

pkcon install-local ~/Downloads/music.ubports_3.0.2_all.click
Installing files              [=========================]         
Finished                      [=========================]         
Fatal error: No such file /home/phablet/Downloads/music.ubports_3.0.2_all.click, or unknown or unsupported content type

Are there any further logs to consult? And where do I actually find the logs on UT?

thanks

I had some similar issues restoring my FP4. At least for that one the installer warns you to have the stock android installed due to the partition layout (iirc). As such I went /e/ -> factory image -> UT.

While installing that factory image I had to disable frp_wipe in the installer script as it would fail the script. Afterwards I had to manually activate the correct slot for booting:

#check the selected slot for booting: should be a or b
fastboot getvar current-slot

#I had to manually set it to boot slot a to boot the factory image
fastboot --set-active=a

after that I was able to boot back into the factory image and could install UT without even setting up the device on android.

I'm currently on a Fairphone 3 and have a FP4 waiting for the installer

@Darkice
I had the same issue with the music app. Default apps get hidden when uninstalling them and don't get properly unhidden upon reinstallation:
https://forums.ubports.com/topic/8851/can-t-re-install-the-music-app/

@picrard said in Issues after one week using ubports on Fairphone 3:

somethimes waydroid crashes completely you have to restart the phone

Install the waydroid helper from the Store. It offers to add a "Waydroid Stop" app. With that you can fully stop waydroid after a crash and usually open it again without rebooting.

I've installed truecrypt(need a program to decrypt containers) after
sudo mount -o rw,remount /
but it doesn't work on ubport ?!

you need "sudo mount -o remount,rw /" the order matters here and the rw has to be the last argument. You can also install the "UT Tweak Tool" from the store. It has a toggle to enable writing to the fs among other things.

@kugiigi
I see. That file does not exist most of the time oO This is my first UT phone, so no copying from anywhere else.
Usually have this file only:

$ cat ~/.config/ut-tweak-tool.sverzegnassi/ut-tweak-tool.sverzegnassi.conf 
[General]
defaultDeviceGU=21

$ ls -l ~/.config/upstart/
total 0

I think you're right that the default scaling changed in OTA24...

$ initctl get-env GRID_UNIT_PX
23

I changed the scaling in the tweak tools to 20 and it did create "your" file:

$cat ~/.config/upstart/ut_tweak_gu.conf 
start on starting dbus
exec initctl set-env --global GRID_UNIT_PX=20

Resetting the scaling in the tweak tools seems to simply delete this file. Not sure why that reverts to 21 though. Maybe the tweak tools call the initctl command explicitly with it's saved default value?

I changed the scaling to 20 in the tweak tools, then manually changed it to 21 in the newly created ~/.config/upstart/ut_tweak_gu.conf. It now stays after a reboot.

I guess I can just change the default value in ut-tweak-tool.sverzegnassi.conf to 23 or delete that file/directory (an re-install the tweak tools) to get UT and the tweak tools to agree on the system state again?

Thanks for pointing out that file and location.

Edit: I changed the stored default value in ~/.config/ut-tweak-tool.sverzegnassi/ut-tweak-tool.sverzegnassi.conf' to 23 and things are behaving as expected again.

Hi all

I have a pair of Sennheiser Momentum 4 BT headphones and they work great for music or calls in waydroid. Unfortunately whenever I try to make or receive an actual phone call they get disconnected from UT.

Is this a known issue or (more likely) specific to this combination of FP4 + Momentum4?

Thanks in advance

I got pyclip installed but it's not enough or working. Don't do this at home

I'm on a fairphone 4 / OTA1 and followed this bug report https://github.com/waydroid/waydroid/issues/309

cd Downloads
wget https://bootstrap.pypa.io/get-pip.py
sudo python3 get-pip.py --prefix=/usr/local
sudo pip install pyclip
sudo apt-get update
sudo install wl-clipboard

Starting waydroid removes all these errors:

waydroidclipboard: Received transaction: 2
Could not setup clipboard

But copy/paste still doesn't work. It does crash the apps I tried it with (firefox/whatsapp). Then again copy-paste between firefox and whatsapp doesn't seem to work at all without those packages installed either...

@TheBird That worked, thanks for the confirmation

Hi all

I recently saw a notification from the "Waydroid Updater" to install a new image inside of waydroid itself. Can this be done from within waydroid or should I update the image from outside directly? And do I need to set r/w flags for the filesystem before attempting the upate?

thanks

for whatsapp you can either use whatsapp web, or use waydroid and run whatsapp in there. Battery life is on the order of 15-20hrs with light use and waydroid always running. You can probably run whatsapp web and just use waydroid to verify the login qr-code (beware the need to get the qr-code in front of the camera )

@kugiigi
correct, the pin entry does not need any confirmation after enough digits are entered. So once the screen is on any random touches on the numpad will lead to a string of login attempts.

@lduboeuf
I have both the greeter and the launcher disabled. it's possible that I failed to enter the pin on the full keyboard as I was a bit rushed.

In any case, given that the bootloader needs to stay unlocked and UT not does support encrypting the home partition(?), I don't think the possible limit bypass by pulling the battery is a large security issue, but it was also not the expected behaviour

Hi all

I managed to activate the screen of my FP4 in my pocket and have it do a few pin entries. The phone locked up displaying a password entry field. Is that supposed to be a different password from the pin I use to normally access the phone?
I entered the pin and was greeted with a message about too many attempts and the phone locking for 5 minutes. I pulled the battery, rebooted, and got in with my pin normally.
I then rebooted the phone due to bluetooth not working properly, and was greeted with the "too many login attempts" message again and had to wait out the last minute of the 5 minute timeout. That seems a bit out of order?

p.s.(a) for any FP4 owner: when pulling the battery make sure your micro-sd didn't come loose... re-seating the battery is a perfect way to guillotine your sd card... ask me how I found out

@Darkice
I had the same issue with the music app. Default apps get hidden when uninstalling them and don't get properly unhidden upon reinstallation:
https://forums.ubports.com/topic/8851/can-t-re-install-the-music-app/

Hi all

Simple question spoilered by the title: What's the current state for backups on Focal? Are there any backup utilities available, and if not, what parts need to be backed up besides the obvious docs/pictures/etc folders?

cheers

@arubislander @kugiigi
Okay, thanks for the info. Those errors messages and symptoms look a bit disconnected from what's going on, but I got the player back