A workaround might be:
pactl set-source-volume 2 300%
(or maybe something less than 300%)
Low recording level seems to be an issue that plagues several SFOS devices.
2 Likes
Well, I just tested again both in a raw, same conditions, and its a light sound in both cases in fact. Its working, but I need to set the playback sound at max level to hear a bit of what was said in front of the phoneā¦ should be 50% volume.
How does you earphone working, guys?
Moved 10mk3 ā 5mk4 today and when a caller speaks I also hear some hiss.
Can it be some setting or do I have a faulty earphone speaker?
I have a crystal clear sound during calls when using the loud speaker mode with a 5mk4.
1 Like
loud speaker is ok for me, too. I have a hiss when not on a loudspeaker
well, I went back to 10mk3:
- not very important, but after restart 2nd sim is always disabled (note, I have PIN set up on it)
- after enabling it (2nd sim) SMS doesnāt arrive.
Put that sim back into 10mk3, immediately all missed sms started to arrive.
This happens to me from time to time too, it should be an initialization race, since the scripts each individually work correctly. I still havenāt debugged it, but now that I am not alone, I should.
That actually has a solution, which I should update the default config with: until then you need to manually install fake-qcrilmsgtunnel-sim2 (you already have fake-qcrilmsgtunnel, which fixes ATEL initialization for first sim)
2 Likes
I managed to make the default Android system c2 audio decoders work in AAS, which enables system-wide audio playback in AAS. Now all audio players using system decoders play audio normally, navigation apps have voice guidance, system sounds and alerts work, in NewPipe one can use the āPlay in backgroundā option to play only audio, etc. Basically, everything related to audio playback should now work.
It only takes adding the following missing lines to /opt/appsupport/etc/appsupport.conf.d/10-hybris.conf file (e.g. right after the # For omx codecs section):
#C2 codecs
Proxies=android.hardware.media.c2@1.0::IComponentStore,android.hardware.media.c2@1.1::IComponentStore,android.hardware.media.c2@1.2::IComponentStore/default
Mounts=/dev/dma_heap dev/dma_heap none rbind,create=dir,optional 0 0
CustomProperties=media.c2.dmabuf.padding=${prop:media.c2.dmabuf.padding}
Thatās all. Just restart AAS and enjoy working audio decoders and sound playback 
Please let me know if the above works for you.
Sadly, c2 video codecs still donāt work so video playback is generally still broken in AAS on a system level (except a few apps like VLC and such which use their own ffmpeg libavc based codecs). Clearly, something else is still missing to make those c2 video codecs work, most probably something just as trivial as the above. Iāll keep searching for it, but it would be great if someone could helpā¦
13 Likes
Just to make sure, you have a dual physical sim device, not esim?
(If so we might have overlooked that, the bootfix should prevent lockout for esim)
Every few months, I feel the pull of the tide to come back to Sailfish. I look around the available ports and the specs of devices, and it always comes up a bit short. It must be small, have a notification LED, and I must be able to buy one.
Last week I found a used 5iv in useable condition, so I thought Iād dive back in.
The ports was easy to install, once Iād remembered how to unlock the bootloader (maybe worth a link to the Sony page in the instructions?).
This is the best SFOS Iāve ever seen. Fast and smooth, exactly as it should be.
As far as I can tell so far after a long evenings testing, everything works! 
GPS is a bit poor, but indoors in device only only, no great surprise.
BT wonāt connect to my car, but thatās pretty common for SFOS devices Iāve owned, so I didnāt really expect it. Maybe I can dig into it a bit when Iāve some time. BT does connect to other devices with no problem.
I might have been missing out by not buying a 10iii years ago!
Anyway - I just wanted to thank you guys for the amazing work. I suspect I may have to start looking for a less battered 5iv for a daily driver.
10 Likes
@wetab73 Thanks for the āhackā. It works for me
1 Like
Iām sure I am not the only one who finds 1 IVās notification LED brightness to be exceptionally poor. Well, it turns out that it is controlled by the ALS sensor and brightness levels for given ALS sensor readings are defined in /etc/mce/20als-defaults.ini file - in [BrightnessLed] section. Just modify the LevelsProfile0 line of that section - simply changing all values to 100 gives a bright and perfectly visible notification LED.
4 Likes
Iāve changed mine from 100 through 4 backwards, so they got to 20, to have some gradation and will report back.
P.S. Seems to be brighter, but not bright enough, will pump it up to through 2.
If I am not mistaken, the problem with ALS controlled brightness of the notification LED is that (unlike display brightness controlled dynamically) notification LED brightness is set only once when the LED is being switched on, and then not changed, even if lighting conditions change. I mean, if you have the phone in a dark place (letās say in your pocket) when some event takes place and the notification LED gets switched on at very low brightness, it then wonāt get any brighter if you take the phone out of your pocket and place it in daylight. The LED will remain dim (matching the initial dim ambient lighting), poorly visible in daylight. Thatās why actually only changing all levels to high values guarantees that the LED would always be clearly visibleā¦.
1 Like
Okay. Iāll keep mine though as it is already visible enough and this behavior might change in the future.
A very minor annoyance, but is anyone else finding the Ambience is always reset on reboot? I donāt think it was happenning right from the start, but now it resets to āFiveā every time.
I deleted the Five ambience as an experiment, and on restart got a surpringly pleasing plain black background, which I could live with. Going into settings, the Five ambience has reappeared, complete with original background image.
I think I remember the C2 having this issue when first launched - but since the C2 had bigger problems, I donāt remember what happened. I should rummage in the drawer and see if it still happens there, but I think it got fixed?
I used to have it right after I bought the 1 IV - when I had encrypted home. Not every single time though, more like every 5th - 10th reboot or so. I reported it in some of my initial posts in this thread.
The problem hasnāt appeared even once since I switched to unencrypted home a couple of months ago. Not a single time.
1 Like
I donāt have it. When you installed, have you also tried to restore some configs from other devices by rsyncāing them. If you did there could be some file/link going wrong.
Re encryption: red herring most probably. I am on encrypted home and have no problem
2 Likes
Yep, I also have this problem on my Xperia 5IV. Sometime after reboot the ambience reset to āFiveā theme.
Also after each reset I have restarted tutorial for different apps - for example: on multitask screen, in calendar app, in clock. Does anyone else face this issue too?
2 Likes
I didnāt import any old configuration or backup, everything was fresh.
I havenāt seen the tutorial restart, but I kept seeing the app hints, until I turned them off under System>Gestures ?
Iām wondering now if it is related to the āSituationsā App, which I use to silence the phone overnight. When it switched to ādaytimeā this mrning, it selected the wrong Ambience, which might be because I deleted the āFiveā ambience yesterday while experimenting (and it came back after restart).