Camera Notification

[mustang7757]

Nothing. Can't long press. Can't swipe it away.

How does it go away?

 

[EMGSM]

How does it go away?

Restart the phone. I installed this update this morning and all has been fine since.

 

[mustang7757]

Nice

Restart the phone. I installed this update this morning and all has been fine since.
View attachment 312725

 

[Serkle K]

The ones it's happening on which Carrier you on ? See if there's a pattern from same carrier and if it's a carrier phone vs unlocked.

AT&T branded.

 

[Serkle K]

How does it go away?

I can go into the settings and force stop, so at least I can get rid of it without having to re boot.

 

[Serkle K]

I got an update a few days ago, but I still get this message.

 

[Gary02468]

I got an update a few days ago, but I still get this message.

Which firmware update do you have? Is it the one that's been reported to fix the problem? There are multiple messages in this thread that say which firmware version fixes it.

 

[mustang7757]

AT&T branded.

I can go into the settings and force stop, so at least I can get rid of it without having to re boot.

That's good , was going suggest that

 

[Serkle K]

Which firmware update do you have? Is it the one that's been reported to fix the problem? There are multiple messages in this thread that say which firmware version fixes it.

I'm guessing it was the November security update. I got it on the 1st.

 

[RickMG]

That's good , was going suggest that

What do you force stop? The camera app? Thanks!

 

[mustang7757]

What do you force stop? The camera app? Thanks!

Yes

 

[RickMG]

Originally Posted by RickMG
What do you force stop? The camera app? Thanks!

Yes

Well, I force stopped it and cleared the cache and it went away. A few minutes later, without using the camera, it came back. Actually, the only picture I took was a screen shot before it appeared. I just restarted.

 

[mustang7757]

Originally Posted by RickMG
What do you force stop? The camera app? Thanks!


Well, I force stopped it and cleared the cache and it went away. A few minutes later, without using the camera, it came back. Actually, the only picture I took was a screen shot before it appeared. I just restarted.

Strange, even with screenshot it happens

 

[evohicks]

After my 2nd update in November yesterday I started to see this message while taking burst shots, it didn't clear so the first time it happened i restarted my phone, 2nd time i did a search and some guy on the Samsung US forum mentioned resetting app preferences ...
Setting > Apps > click on the 3 vertical dots in the top right corner > click on reset app preferences > click reset.
This will mean you will need to set permissions again so be warned, but I haven't seen the message since yesterday.

 

[RickMG]

Here is the fix from digital trends:

https://www.digitaltrends.com/mobile/samsung-galaxy-note-10-plus-problems/

 

[Liorid]

Hello,today i got an update from the camera app and it fixed the problem

 

[Gary02468]

Here is the fix from digital trends:

That's a workaround, not a fix. The camera should work properly without having to disable background management for the app. And the latest version (9.5.01.5) fixes the problem.

 

[RickMG]

That's a workaround, not a fix. The camera should work properly without having to disable background management for the app. And the latest version (9.5.01.5) fixes the problem.

View attachment 312964

I seem to have the latest update according to my settings but still had the problem. How are people getting updates I can't get? I have an unlocked version. Also, where would I see my version number? Thank you.

 

[RickMG]

That's a workaround, not a fix. The camera should work properly without having to disable background management for the app. And the latest version (9.5.01.5) fixes the problem.

View attachment 312964

One other thing. It says that if you don't close the camera right away you won't get the warning. So is just a work around for those of us who take a photo and close the camera, I think.

 

[willpooted]

Good news is that the Android 10 beta fixed the issue for me