[Galaxy S3 Neo Original Android Development] helloyello:
[MENTION=9002492]andriodking[/MENTION]

As [MENTION=8750475]Humaxxx[/MENTION] already mentioned, use the ViPER4Android FX 2.7 APK (not Magisk module!) and only provide root access for it in Magisk. I'm using it myself like that and after an OTA, when the phone starts the first time, ignore ViPER4Android FX and first uninstall Audio FX (it will be installed by default on every OTA and conflicts with ViPER4Android FX), then reboot. After this reboot, ViPER4Android FX 2.7 is notifying me that it wants to reinstall the driver, I accept it and then reboot again. After that, everything works just fine.

https://labs.xda-developers.com/store/app/com.pittvandewitt.viperfx

[MENTION=10132973]Merftj[/MENTION] & [MENTION=8750475]Humaxxx[/MENTION]

I can confirm the issue with the Bluetooth, noticed it myself with the lineage-16.0-20200310-nightly-s3ve3gxx-signed update. I'm a heavy BT user, 90% of the time I'm using a BT Headset. After a while, in close proximity to the phone 1-2 meters, usually after more than 20-30 minutes, while using the Phone App (not happening with messenger apps apparently) I'm loosing the BT connection - I'm still able to hear the other persons, but they aren't able to hear me. If, while still on the call, I go on the Phone App - current call and switch the audio to Phone and back to BT, it works again. Worth mentioning that when I'm loosing the BT link, moving too far away from the phone, the BT Headset notifies me with a short Beep, that feature/functionality still works and it's not the case with this reported issue.

I tried to unpair (remove old connection) and repair the BT Headset, tried also a second BT Headset - older one I don't use anymore - and still experiencing the same issue. Something went wrong in the lineage-16.0-20200310-nightly-s3ve3gxx-signed OTA. This never happened in lineage-16.0-20200219-nightly-s3ve3gxx-signed

[MENTION=8750475]Humaxxx[/MENTION]

I didn't have time to update our last discussion. I finally managed to perform an OTA from lineage-16.0-20200219-nightly-s3ve3gxx-signed to lineage-16.0-20200310-nightly-s3ve3gxx-signed and using this image for more than a week now without any issues (other than the BT mentioned above). When I first noticed this BT issue, I restored the lineage-16.0-20200219-nightly-s3ve3gxx-signed backup (all partitions, including EFS) with TWRP and did the OTA again, without resolving it. A second attempt was to restore the backup, perform the OTA for lineage-16.0-20200310-nightly-s3ve3gxx-signed and remove ViperFX and leave the default AudioFX in place, considering that maybe ViperFX is breaking the BT. No success with this approach either.

Maybe some of those March security fixes broke something / or the updated BT driver/kernel? (if any). Funny that I'm only experiencing this with the Phone App and not with other messenger apps - I'm using Signal a lot and it works just fine.

---------- Post added at 03:23 AM ---------- Previous post was at 03:08 AM ----------

You could use OpenCamera (way better than the stock LineagOS one) :

https://f-droid.org/en/packages/net.sourceforge.opencamera/

And set the storage in any SD Card folder you want:

Open Camera > Settings > More Camera Controls > toggle on Use Storage Access Framework then navigate to /storage/Micro SD card id/DCIM/Camera & Save Location.