# [3.0.2.8] Can't change Ambiences anymore [answered]

Hi fellow sailors! I was recently met with weird behavior when trying to change the ambience on my Jolla 1. Some days ago, I put it on the "Silent" ambience, and it seems to be somewhat stuck on that ambience since then. I can't change ambiences from the top menu anymore, only from the settings (and even then it often doesn't work). What's even weirder is that, when I am able to change, the background image and the system sounds change, but the menu colors stay blue-ish, as if "Silent" was still activated.

I also encounter odd errors when opening Storeman about certain folders in /var/temp not being writeable, not sure if it has anything to do with that. Any ideas for what I should try before just factory-resetting the phone again?

edit retag reopen delete

### The question has been closed for the following reason "the question is answered, an answer was accepted"by pawel close date 2019-04-24 08:57:18.288309

Try this from terminal: systemctl --user restart ambienced.service

( 2019-04-20 13:30:56 +0200 )edit

Jolla1 ? What about btrfs balance ?

( 2019-04-21 10:14:17 +0200 )edit

@pawel it seems to actually have something to do with that - I ran btrf-balancer balance and it failed around 80%, yet I gained an additional 500MB of space and it seems to have fixed the ambiences issue at least. But how can this be the cause? I had more than 3GB free on my phone's internal storage...

( 2019-04-22 00:42:51 +0200 )edit

Hi, Very similar problems here, also with Jolla 1 device. Additional issues, I'm not able to switch off the Location , and sadly, after trying to find solution, I have found this btrfs related fixes, however I can't turn on the remote connection, so I can't do anything with root privileges. I don't know how to continue. I'm planning to upgrade to an Xperia XA2 device, but a bit later on, not now. It would be nice, if anyone of you have a solution.

( 2019-04-23 10:05:50 +0200 )edit

Since then I'm not able to uninstall applications, and it seems everything is related to the writing issues @CHZK just mentioned. If I check the storage in the options, 7.9GB used, 5.9GB available. But lot of applications said, the disk is full.

( 2019-04-23 16:04:47 +0200 )edit

Sort by » oldest newest most voted

Okay, so I've found my solution. About 6 months ago, I did a factory reset, which led to the same problems that this guy encountered: https://together.jolla.com/question/14633/bug-factory-reset-no-storage-left/

After the reset, the space taken up by Sailfish OS system files was a whopping 8GB! Combined with brtfs allocation problems similar to those described here, it lead to btrfs showing me 100% of chunks being allocated when running btrfs-balancer allocation: https://together.jolla.com/question/30822/root-and-home-disks-full-and-causing-various-problems/

In order to fix this, I first went ahead and ran mount -o subvolid=0 /dev/mmcblk0p28 /mnt/ as root, followed by btrfs subvolume delete /mnt/@_old to delete the superfluous backup files. Lo and behold, the amount of space taken up by the system files shrunk back to 3GB. Then I ran btrfs balance start -dusage=25 /, and it told me that 4/17 chunks had been reallocated, leading to only 52% of chunks being allocated in total. Finally, and this is important, I ran umount /dev/mmcblk0p28 in order to unmount the btrfs partition(?). If you don't do this, your phone might not boot correctly next time you turn it off and on again!

tl;dr Jolla needs to get their shit together when it comes to automatic filesystem maintenance. This should never have to be done by the user! Supposedly Jolla checks for allocation and all that with every update, but the sole fact that factory resets end up taking valuable space on the device (without even telling you about it) is just ridiculous.

more