Since a week or two, the icons indicating the camera and the microphone are off does not appear anymore in the top bar of the phone, when the dedicated physical switch is off.
When the switch is off, the camera and mic are off too, but when the switch is on, only the microphone is on.
Any idea to remedy the problem or to investigate the issue?
I don’t know how to investigate.
But, I am seeing buggy behaviour with a different icon in the top bar, the “On/Silent/Quiet” icon. I think it started a few weeks ago as well. The “On” and “Silent” icons are reversed, when the pone is “Silent” it does not show any icon but, when the phone is “On” it shows the Silent icon >…< confusing but I can live with it.
EDIT: Please ignore my message. I just did not understand how the icon is supposed to work. When the menu icon is blue/active it means that phone is NOT on silent, and when is off it means the phone IS on silent.
reflash in order to verify whether the problem happens on a clean system
restore the image from the first bullet point
So the overall effect to the phone is “no change” but you know whether the problem happens on a clean system or not - hence you have more information about the likely cause and the likely solution.
I use app from flatpak on the phone, and on a laptop too. I recall, when re-installing the laptop that I was unable to properly restore the data and especially the configuration of those apps. According to some posts found on the net’, I just need to ensure I have a backup of $HOME/.var/app. However, I do recall i did that and yet after restoring the app data, The re-installed app was not seeing the configuration, it looks like at the time.
So, do you know if anything else is needed to backup properly flatpak data and configuration?
i am in the same situation, since i installed the last update, the camera symbol and the microphone do not appear, also the same thing happens to me, the microphone still works perfectly, but the camera has stopped working. the switch works fine but the camera does not react. i mean that now the switch only activates or deactivates the microphone because the system does not detect the camera, and obviously i have tried to reboot, i have tried with 3 different camera apps. and nothing, as if the camera does not exist.
Indeed. For a given application, that may or may not be reliable. However that isn’t what I was suggesting.
What I was suggesting was to image the entire disk in the first step and restore the entire disk in the third step. So that there is no need to worry about pieces of directory tree that may or may not have been validly backed up and may or may not restore properly.
The procedure I suggested was strictly diagnostic. It is guaranteed not to fix anything.
So if the only content on the SD card is a current backup, it won’t matter either way if it were wiped out - because this procedure involves making a new backup onto a host computer.
From there - if you found that temporarily running the reflashed phone, the problem goes away - you could even mount the reflash disk image (if you kept it) and the backup disk image on the host computer and try to work out what file changed - if it’s that kind of problem.
For the record, when I reflashed from amber to byzantium I just redid everything from scratch, with very limited restoring of any settings etc. by restoring files. Yes, that is more painful (more work) but it is more reliable and you probably get a cleaner result.
I confirm that after reflashing, the phone behave as expected with regards to the camera and microphone.
So, now we know it is something in my original system, how to proceed to find the culprit?
Or, should I simply reinstall everything and copy back any data, from the backup image I have performed?
BTW, where is located the addressbook and where are located the phone call and text (SMS) logs?
I think it depends on how much time you want to spend on it. In my opinion the easier and cleaner option is to accept the reflash as it is and then re-establish your environment.
I’m not certain but I think: ~/.purple/chatty/db/chatty-history.db
I’m not certain but I think: ~/.local/share/calls/records.db
When I reflashed I didn’t bother to copy over texts or call history but I did copy over contacts.
As always when messing around with a .db file, make sure that the file is not in use when replacing it - and keep a copy of the original in case things go pear-shaped.
After reflashing the phone, and before restoring the configuration files, I configured the phone to access the wifi to ensure it is up to date.
After the update, I fall in the same problem again. So it is something in the last updated packages that seems to mess up with the camera. But, it is strange only a few of us suffer from this problem.