Hi!

After a vendor image update about 2 weeks ago I can't unlock my waydroid installation anymore. I tried to erase and reinstall waydroid, without erasing the personal data, to get the recent vendor image, but the behaviour does not change: waydroid is starting, but after trying to unlock it (with the correct pattern, it gave an error message after an incorrect try) it returns to the screen asking me to unlock it and so on...

I am using a fairphone 3, recent 20.04 dev channel installation, waydroid installed via waydroid helper app.

Any ideas how to solve without erasing the data?

@Ken1971
Hi!
After a few failed attempts trying to save the data of my waydroid installation I was able to solve it, but had to erase all the user data, and re-install everything I had running in the waydroid installation. 24.04 is not yet available for Fairphone 3, so its 20.04 I'm using.

@Ken1971
Yesterday the same problem appeared on my Fairphone 3.
The log just tells me that the session is starting, and that the /dev/anbox-binder has appeared, nothing else.
Any precautions needed for the reinstallation? I would hate to loose my data within the waydroid container.

EDIT: removing and reinstalling did not change it - waydroid still hangs at the start.

So I gave it a try and set all the ownership in /home/phablet to phablet:phablet, and after a reboot the app actually found some of the new files.

Looks like the app can't handle mpc files properly; or at least can't read the tags - they all end up in one "Unknown album" - but that's a different problem.

@arubislander Yes, I did, and I had to change the rights of the files in /music, too. I opened an Issue (nr 104) on the gitlab page, see
https://gitlab.com/ubports/development/apps/lomiri-music-app/-/issues/104

@arubislander Any idea how to find those?

Found at least something: The mediastore.db in ~/.cache/mediascanner-2.0 had the wrong rights, I changed the ownership from root:root to phablet:phablet, so the app starts again.
But I still have not found a way to refresh the database for the Music app to show the new files I have added to ~/Music. I recall that this happened automatically, but it does not - or perhaps not any more?

Hi!

I have yet another problem with the Music App: It does not start anymore, it just tells me that there is no music to be found; the log is flooded with literally hundreds of messages

lookup () called on invalid MediaStore

When trying to play a file from the filemanager choosing the Music-app a message appears telling me that the app is waiting for data, after a few seconds I am asked to wait longer or to quit - waiting leads to a seemingly endless display of the message, but nothing is played.

Is there a way to force the app to reread the data, as it does at first start? Is there some kind of db-file that could be renewed?

Device is a fairphone 3, dev channel 20.04

@jojumaxx Hi!
I have similar problems, looks like using waydroid and mounting ~/Music to it causes problems. The music app can't read the files anymore because the mounting changes the owner. See https://gitlab.com/ubports/development/apps/lomiri-music-app/-/issues/104

Hi!
Futify does not connect anymore, and, what is worse, Spotify considers it a be a security risk. Yesterday I tried to use futify and to log in with my username and password without success; today I got an email telling me that the had to reset my password because of "suspisious activities". See https://forums.ubports.com/topic/10567/spotify-blockt-futify

So, it just doesn't work anymore.
greetz
hank

@DeadBattery
My fairphone 2 works with OTG, version is 16.04 devel, (2023-04-17)

@lakotaubp

The error message is still there, I get it every time I open an ubports-page outside the forum. After pressing the "OK" - button, the pages seem to work fine - I didn't order anything to check it ;-)!

This is the error box; I use an up-to-date firefox 100.0, running on Ubuntu 20.04.

Bildschirmfoto vom 2022-05-14 19-54-43.png

Hi!

Something's still amiss; I get an error when opening the shop; message as follows:

Error:
Error: Permission denied to access property "apply"

https://ubports.com/web/content/155099-7063fc3/9/web.assets_common_lazy.js:1143
Zurückverfolgung
trigger@https://ubports.com/web/content/155099-7063fc3/9/web.assets_common_lazy.js:1143:31
trigger/<@https://ubports.com/web/content/155099-7063fc3/9/web.assets_common_lazy.js:1148:258
each@https://ubports.com/web/content/155099-7063fc3/9/web.assets_common_lazy.js:624:170
each@https://ubports.com/web/content/155099-7063fc3/9/web.assets_common_lazy.js:615:192
trigger@https://ubports.com/web/content/155099-7063fc3/9/web.assets_common_lazy.js:1148:229
attach_handlers/<@https://ubports.com/web/content/155100-0a0c73f/9/web.assets_frontend_lazy.js:1032:513
dispatch@https://ubports.com/web/content/155099-7063fc3/9/web.assets_common_lazy.js:925:447
add/elemData.handle@https://ubports.com/web/content/155099-7063fc3/9/web.assets_common_lazy.js:911:166
trigger@https://ubports.com/web/content/155099-7063fc3/9/web.assets_common_lazy.js:1142:227
trigger/<@https://ubports.com/web/content/155099-7063fc3/9/web.assets_common_lazy.js:1148:258
each@https://ubports.com/web/content/155099-7063fc3/9/web.assets_common_lazy.js:624:170
each@https://ubports.com/web/content/155099-7063fc3/9/web.assets_common_lazy.js:615:192
trigger@https://ubports.com/web/content/155099-7063fc3/9/web.assets_common_lazy.js:1148:229
attach_handlers@https://ubports.com/web/content/155100-0a0c73f/9/web.assets_frontend_lazy.js:1032:534
start/<@https://ubports.com/web/content/155100-0a0c73f/9/web.assets_frontend_lazy.js:1032:349

I've seen it on other ubports pages as well...

Hi!

Perhaps it is an "app issue"? Some apps are restricted to a certain screen orientation. You could check in ~.local/share/applications, in the .desktop files. Some apps have a setting called

X-Ubuntu-Supported-Orientations=

Possible values are

primary, portrait, inverted-portrait, landscape, inverted-landscape

perhaps it helps to change it there.

@mrt10001 I have another BQ Aquaris m10 FD running Ubuntu Touch; the wifi bug is still not solved, so I can't use both devices within the WIFI network at home - I tried to change the address, but didn't succeed.
The whole thing started out when I tried to use twrp on the m10, I wanted to root it and to try Lineage or something similar... But that's a different story.

OK, sometimes you don't see the forest for the trees... FInally I was able to use the flash tool; a little "sudo" helped a lot...

I reinstalled an Android 8.1 version, and afterwards I was able to use fastboot to relock the device.

Thanks for your support!

@mrt10001 I could try, but I doubt if that changes anything. After a night of reboot loops the battery is more or less drained, the device is "shut down". But as soon as I connect an usb cable and power is provided again, the boot loop starts again, too.

Is there some hard reset tool available for Ubuntu Linux to force a reset? I found something like that, but it seems to be a windows tool.

EDIT: Tried to disconnect and then press the power button; as soon as I reconnect, the device tries to loop again, even with the the almost drained battery it vibrates about every 5 seconds. Same behavior as before with the charged battery.

@mrt10001 No chance using the vol+ button that way, the device just just keeps looping, no matter in which order I push or release buttons. I have already opened up the device, have to check how to disconnect the battery. I think I saw a youtube video somewhere how to replace the battery, I'll search for that.

EDIT: I was able to disconnect it, but as soon as I reconnect the battery, the loop starts as before....

@mrt10001 It simply does not switch of, it keeps restarting...

@mrt10001 No use, no matter for how long I press the power button, it keeps looping into the same state. I guess I have to wait till the battery is completely drained before I can try anything at all.

lsusb does not show the device, it shows up only when I keep power, vol+ and vol- pressed at the same time. adb does not find it, not fastboot, no matter if I use USB2 or USB3 ports. I tried different cables as well (and those worked with the ubports installer).