Small update: in the corresponding github issue about not working external display, someone suggested to add one line to the apparmor config, because the root cause is a “permission denied” on some file.
CardDAV : the existing account from OTA3 was still there but not updated, I re-run the sh script and now I have two CardDAV accounts, so the majority of my contacts are doubled. To do: understand how to delete one of the two accounts
To check also if the crontab was successfully set-up by the script
CalDAV : strangely the script doesn’t work at all ! [INFO @caldav] @caldav/caldav: log in succeeded, but server refuses access - contact server operator Workaround = use the interactive method (Open the Calendar app, click on the little calendar icon in the top right corner and select “Add internet calendar > Generic CalDAV”. Enter your calendar URL as well as your username and password to complete the process.) -> this works
Thanks a lot for your testings! Unfortunately, I didn’t succeed to install UT through the installer 0.1.21 on Windows 10. I tried the older versions 0.1.20 and 0.1.12 but it’s not working neither. Is there an other way to install it or do I have to try each older version of the installer? (Or is it just Windows 10 related?)
I can’t give a definitive answer. The older versions of the installer where people reported success were 0.1.9 and 0.1.12. And it is said that mac and windows versions may give more trouble than the linux versions. In the Telegram install group it is suggested to use a Ubuntu 16.04 live USB stick when the win installer doesn’t work.
Not sure why it fails for you, so no idea if the above version is of help at all. But it has somewhat more debug output in case of problems. So it might help finding the cause of the failure on windows.
Two things come to mind … either the “Basic Display Adapter”, which is a fallback driver in Windows used in case there’s no other graphics driver installed (and which oftentimes works more hasslefree for basic needs than Nvidia/ AMD/ Intel drivers) … or the “Wireless Display Adapter”, which is an external hardware adapter.
Calibrating a smartphone compass should be OS-independent … move the smartphone through the air following an imagined “8” (or infinity loop) in different directions (or dimensions) until the respective App doesn’t complain anymore.
Checking OS-independently whether the compass is right is harder … Sun? Stars? Known orientation of nearby streets or railways?
That’s what I’m saying. In Xompass app, the compass is not moving if phone is rotating. Also the SensorStatus app show no numbers in compass tab, so my guess is, that UT is not even avare, that there is an compass in phone.