(another) night mode bug

I believe it to be the app that has to be updated to support Night Mode.

If you mean that "nest" should be updated, that is the silliest thing I've read today. Are you suggesting that if Samsung decides to add some random proprietary UI element to their firmware, that every application developer in the world has to jump and update their application to work with Samsung? (This is even more amusing when you consider how developer unfriendly samsung is.)

Anyway, I don't think that it's anything that nest can (or should) fix. This is an issue with how Samsung (not nest) is rendering the notification when their proprietary "night mode" is turned on
 
This. I wouldn't think it it would be any system settings when no other app behaves like this.

I've yet to find another app that displays the same particular combination of title, text, thumbnail and animated gif in the notification panel, so it's difficult to suggest that no other app behaves like this.

I'm inclined to believe that Nest (a google company) is doing things properly for the android OS, and that Samsung is the one to blame here. The problem is that I'm finding it impossible to get Samsung to even investigate the issue.
 
If you mean that "nest" should be updated, that is the silliest thing I've read today. Are you suggesting that if Samsung decides to add some random proprietary UI element to their firmware, that every application developer in the world has to jump and update their application to work with Samsung? (This is even more amusing when you consider how developer unfriendly samsung is.)

Anyway, I don't think that it's anything that nest can (or should) fix. This is an issue with how Samsung (not nest) is rendering the notification when their proprietary "night mode" is turned on
Night Mode was baked into Android P which gave Samsung the ability to use a Native Night mode. They did have to add their touches to Night Mode for OneUI but it's a Native Feature of Android P. So yes developers need to accommodate that added feature. Have a nice day.
 
No theme. As mentioned in the OP, I turned on "night mode" in Settings->Display. That alone seems to be causing the problem.




I'd suggest checking google play for "tasker." It'd take me months to describe everything it is. For the purpose of this discussion, however, it's a persistent notification that's just telling me that my phone is connected to a specific wifi access point.

From the looks of it, @williams448 has the exact same issue and is also using night mode. williams448, try pop into Settings->Display and turn OFF night-mode. Then clear any nest notifications and cause another nest notification... I suspect it'll appear just fine then.

vader4633, this isn't on the lock screen at all. Oddly, the lock screen notifications appear fine.

I'm trying to help you figure your problem out , I dont have your phone in my hand . Now you want to figure this out then be patient and work with me , if not that's fine also .
 
Last edited:
I've yet to find another app that displays the same particular combination of title, text, thumbnail and animated gif in the notification panel, so it's difficult to suggest that no other app behaves like this.

I'm inclined to believe that Nest (a google company) is doing things properly for the android OS, and that Samsung is the one to blame here. The problem is that I'm finding it impossible to get Samsung to even investigate the issue.
Google can't even get Night Mode right on their own Pixel devices so I'm not surprised they can't get their own app to work either. Complain to Google and Nest instead of trying to condescend people that are trying to help you.
 
I'm trying to help you figure your problem out , I dont have your phone in my hand . Now you want to figure this out then be patient and work with me , if not that's fine also .

Please pardon me if you took my post as being impatient or hostile towards you. I'm just sick of (and amused by) people who think that Samsung can do no wrong, that all their products are Godly, and if there's some issue with their firmware, it's the user's fault for having bad expectations. (As a professional software developer, I've also had my share of run-ins with bad code from Samsung. As a hobbyist developer, I've even seen bad code from them that would brick their own devices. Obviously, those experiences have colored my view of them.)

That being said... Tasker really is a bit involved to explain in a single forum post. I've been using it for.. 6 (?) years and I still haven't explored it fully. What's it's being used for in this case is that when I connect my phone to a specific AP, it lowers my volumes and keeps them lowered as long as I'm connected to that AP. (If you're familiar with Tasker, it's a tasker profile.)
 
Google can't even get Night Mode right on their own Pixel devices so I'm not surprised they can't get their own app to work either. Complain to Google and Nest instead of trying to condescend people that are trying to help you.

So... if something works fine with one setting on a phone, but it doesn't work when a proprietary "night mode" is turned on, you don't think it's the fault of the "night mode"?

Keep in mind that android is specifically designed for backward compatibility. Even if there was a supported global "night mode" in android, an app isn't required to support it and the OS should handle things properly. The problem here is Samsung's modification of the OS.
 
So... if something works fine with one setting on a phone, but it doesn't work when a proprietary "night mode" is turned on, you don't think it's the fault of the "night mode"?

Keep in mind that android is specifically designed for backward compatibility. Even if there was a supported global "night mode" in android, an app isn't required to support it and the OS should handle things properly. The problem here is Samsung's modification of the OS.
It can be a Samsung issue but night mode is not a proprietary feature. It's part of Android P. But yeah I'm sure Samsung also applies some kind of dark theme when Night mode is turned so it's definitely possible. Try Turning night mode off and try using a few different dark themes from the theme store (there are plenty free ones) and see if the issue occurs. If it looks fine with a dark theme then that'll probably have to be your work around until Samsung addresses the issue. These notification issues happened on my Pixel 2XL in the early days of the Android P official release but were later fixeda when developers updated the apps. Which is why I mentioned it can be the app itself So who knows where the problem really is.
 
BTW, I have night mode off and use Black_Edition_v2 dark theme by MINU and it does a good job as a System wide dark theme. If you don't like the icons you can use different ones from the Galaxy store as well.

Some notifications will still have a white background but the one in the screenshot below used to show like your nest app until Blackberry updated it.
0a28b05e777aa2969b10db209346e0b1.jpg
 
Please pardon me if you took my post as being impatient or hostile towards you. I'm just sick of (and amused by) people who think that Samsung can do no wrong, that all their products are Godly, and if there's some issue with their firmware, it's the user's fault for having bad expectations. (As a professional software developer, I've also had my share of run-ins with bad code from Samsung. As a hobbyist developer, I've even seen bad code from them that would brick their own devices. Obviously, those experiences have colored my view of them.)

That being said... Tasker really is a bit involved to explain in a single forum post. I've been using it for.. 6 (?) years and I still haven't explored it fully. What's it's being used for in this case is that when I connect my phone to a specific AP, it lowers my volumes and keeps them lowered as long as I'm connected to that AP. (If you're familiar with Tasker, it's a tasker profile.)
I understand the frustration, but I need to know what's on the phone to better help you as so many things people download from themes like substraum or application cause issues .
So i try to work with you see if we can solve this or come to a conclusion .
Thanks for responding back , Were cool !
 
So... if something works fine with one setting on a phone, but it doesn't work when a proprietary "night mode" is turned on, you don't think it's the fault of the "night mode"?

Keep in mind that android is specifically designed for backward compatibility. Even if there was a supported global "night mode" in android, an app isn't required to support it and the OS should handle things properly. The problem here is Samsung's modification of the OS.

It could be a bug in the code , but for 1 app well at least the other poster mentioned just 1 it's hard to believe as it would affect all of them .
 

Forum statistics

Threads
956,427
Messages
6,968,211
Members
3,163,542
Latest member
04ijordan