I noticed that after the last update (UI 4), the Facebook Messenger causes a momentary (about one-two seconds) screen freeze after hiding the chat window. I think that hasn't happened before update. I tried cleaning application cache but I don't see any difference.
Good morning @Rekon, thanks for reaching out. In some cases, the 3rd party apps also need to be updated and optimised for the new update. Is this occurring with multiple apps or only Messenger?
Some steps to try:
1. Restart your device. In some cases, restarting your device after an update assists in clearing in clearing any background data and help the device function more smoothly with the new update.
2. Check for Messenger app updates.
3. Uninstall and reinstall Messenger.
If the issue persists on multiple apps, I suggest sending an error report via the Samsung Members app for this to be investigated. Error reports are sent to our team to identify any deviations in your device performance, once analysed, our team will get back to you with a response to advise further.
To send an error report:
Samsung Members > Get help > Error reports > select issue category > describe issue and frequency > Tick ‘send system log data’ > Send in top right.
This issue for now is only visible in Messenger. I tried all of the steps, sadly nothing changed. Also tried to report the issue via Samsung Members, but they did not found anything suspicious in logs.
FYI it's unlikely Samsung device specific as my LG LM-G820UM (AT&T G8) was only just updated to Android 11 (January 2022) and it's now experiencing system not responding issues when using FBM chat-head/bubbles.
It occurs after attempts to shift focus off the FBM Android APK Chat-head/Bubbles function.
At times it requires a system reboot although most times changing device focus, or waiting a few seconds, returns system response.
Have had success using power button to lock screen then unlock via the fingerprint sensor on the LG G8.
Like others I've reported this to FB for support to correct the code (hopefully). It, obviously, should not be occurring with any properly tested code.
It's certainly more than bothersome since FBM is a communications APK.
