The N10 auto-brightness feature doesn't work right, as everyone knows. It randomly dims and brightens in an annoying way. I'd read it was a software issue - something to do with JB 4.2 - so I tried two different auto-brightness apps from Google Play, both of which get good ratings, and to my surprise I had the same problem with both of them. When the brightness depends on my N10's light sensor, the screen keeps dimming and brightening randomly. The app I have installed (but disabled) now is "Custom Auto Brightness". I wish I could use it because it looks very good.
The fact that the problem appears regardless of the software suggests to me that the problem is in the hardware - there's something wrong with the data put out by the light sensor. Does anyone have any info or insight about this? A workaround would be so nice.
I'm having a couple issues with my nexus 4 after upgrading manually to Lollipop with the system image from Google Developers.
Sometimes, when the screen goes idle and turns off automatically or when it's turned off manually using the power button, the screen flashes on a higher brightness and shows the lockscreen before turning off. (I'm guessing the desired result is that the lockscreen should appear 'on screen' after the backlight is completely off).
What this causes is that when turning off the screen, the screen dims with the animation (fade to black and turn off), but before (and sometimes after) the animation is complete, it flashes for a few milliseconds displaying the lockscreen/background, even when locking the phone inside an app.
I could upload a video of the issue at a later time.
This bug didn't happen on any version/rom that went through my phone (many stock, many custom). Although I haven't tried installing another 5.0 ROM / AOSP.
The update also brought back a [hardware?] issue this Nexus 4 unit also has had since I got it. When dimming the screen using the brightness slider, sliding to the lowest setting turns off the backlight completely (effectively making the screen pitch black instead of dimming). This issue has been reported before and I was using Gravitybox to override the system lowest brightness level. Could these two issues be related? (Note that this issue didn't trigger this behavior before).
This issue has been reported by other users here:
http://forum.xda-developers.com/nexus-4/help/zero-brightness-t2168071
http://forum.xda-developers.com/nexus-4/help/problem-nexus-4-brightness-t2052857
https://www.youtube.com/watch?v=dvgt17sKQsU < this shows the screen going pitch black at lowest brightness, it happens either from the widget, the slider, and the option in settings.
Any ideas on why it happens or how can it be corrected?. Do you also have this issue?.
Many thanks in advance.
Hello to everyone,
I have a Note 4 N910F with stock Android 5.0.1 and i have seen some issues with the ambient display.
With this feature the phone is supposed to turn its screen on every time a notification arrives. My phone turns its screen on for some notifications like messages and viber but for other applications the screen doesnt turn on. Allthough if i press the home screen the notification is there on the lock screen.
Its kinda annoying thing because thats one of the major functions about android lollipop.
I would like to mention that its not any settings problem because all the notifications for its application are enabled on my phone.
If anyone knows if this is normal or software issue or application issue it would be very helpful. Thank you.
First of all... How did you get ambient display to work?
I don't have the option although sammobile posted a video with a lollipop rom having this feature.
I dont know if i am right but by ambient display i mean that when a notification arrives it appears on the lock screen and the screen turns on.
For me for some apps the notification is on the lock screen and the screen doesnt wake but for other apps like messages and viber both notifications and screen wake is there.
for that reason i use an app that whenever there is a new notification the screen turns on.
giannisgr1 said:
I dont know if i am right but by ambient display i mean that when a notification arrives it appears on the lock screen and the screen turns on.
For me for some apps the notification is on the lock screen and the screen doesnt wake but for other apps like messages and viber both notifications and screen wake is there.
for that reason i use an app that whenever there is a new notification the screen turns on.
Click to expand...
Click to collapse
Hey. Could you share your csc files so that I can enable amibent display on my device?? Your device must have it only because the country you're in.
That's not ambient display. This function is missing in the recent release of 5.0.1 touchwiz. Sammobile did show it being there in the sound and notification menu above the daydream option but seems Samsung left it out in the release. I'm thinking that the delay with release for other European countries is due to bugs and missing items, I'm not sure. The original delay was to get tw lollipop to work with the vr headset. At present its hit and miss with notifications lighting up the screen when they arrive. Some apps do it and some don't. Ambient display is where you pick up the phone and notifications are shown in black and white for quick glance as is the case for nexus 6 lollipop or cm12. I'm hoping the rollout to other countries well have solved the missing ambient display and the priority notification not having any time option like in blocking mode on kk.
Sent from my SM-N910F using XDA Free mobile app
giannisgr1 said:
Hello to everyone,
I have a Note 4 N910F with stock Android 5.0.1 and i have seen some issues with the ambient display.
With this feature the phone is supposed to turn its screen on every time a notification arrives. My phone turns its screen on for some notifications like messages and viber but for other applications the screen doesnt turn on. Allthough if i press the home screen the notification is there on the lock screen.
Its kinda annoying thing because thats one of the major functions about android lollipop.
I would like to mention that its not any settings problem because all the notifications for its application are enabled on my phone.
If anyone knows if this is normal or software issue or application issue it would be very helpful. Thank you.
Click to expand...
Click to collapse
I've enabled it
http://forum.xda-developers.com/not...lay-note-4-t3173985/post62223793#post62223793
Screen noise/flicker upon turning screen on
Upon turning on the screen, there is a slight flicker/staticy looking noise. Toward the bottom of my lock screen. It's easily replicated, but it doesn't do it every time.
I just want to know if it seems like a defect or it could easily be fixed by an update. Motorola might not even know about it yet.
Yeah mine does it sometimes, but not all the time
Sent from my XT1575 using XDA Free mobile app
I'm getting that too.
I filmed mine in slow motion when this happens on it and it appears to be an android software bug. It flashes the home screen then pulls up the latest app or vice versa. its so fast it looks like its just noise though.
you guys sure you didnt turn on the option for it to make a noise on unlock?
Are you guys or anyone else having this problem while being rooted? Because, I only started noticing this problem after I rooted
It happened to me before being rooted, if I had Moto Display on it never showed, it was only until switching to Ambient Display, or to neither Moto or Ambient Display that it started showing up.
Always running Notification
May be because of any always running notification. I too had same problem. Then I uninstalled the app that always used to have a notification running. Now the problem seems to be less frequent or not anymore.
Hi everyone
I want to share a workaround to all of us who owns a defective S5
Symptom: You unlock your phone and it doesn't show anything. Actually, the phone is working. Capacitive buttons light up and you may heard some activity in the phone
Your phone has a defective screen. There are a lot S5 which have this problem, according to several forums. After several tries, unlock and lock over and over, the screen light up and you are able to use your phone. The problem is when you receive a call and you want to know who is calling you, the screen doesn't illuminate and you won’t be able to know who is.
Here's a workaround which makes your powerful S5 usable and take out from your drawer.
Solution:
The more effective way to fix it is: change defective screen! But sometimes it could cost as much as a new phone, or simply you can't afford it, and it's better to change your phone instead, and you put your S5 in a drawer.
The technical explanation of this problem is: Screen doesn't receive enough electrical current at low brightness levels (maybe the flex is defective, get old, etc)
Most probably the wake up problem exist together with screen flicker at low brightness levels
The wake up problem rises up more in dark environment, when light sensor make low bright screen
The lock screen light up screen, with a dim effect: when you lock the phone, it slowly turn screen off, and when you unlock, it make and effect of dim screen.
When you are is in dark environment, the effect is very slow, preventing the screen illuminate because the technical problem explained before.
When you are in very light environment, you lock screen and sensor light make the screen very brilliant and chances are you defective phone wakes up correctly.
We can use an app which give us complete control over brightness subsystem. I use an app called Velis AutoBrightness:
Once installed from Play Store, it shows a Setting Wizard. Follow the instructions. Below are some notes
• 1/7: Welcome Screen
• 2/7: How bright... Most probably is your phone always have flicker in low brightness. Choose "AMOLED" or "AMOLED bright". By the way choosing any one of those cure always minimum brightness failure!
• 3/7: Choose High sensitivity
• 4/7: On, if you want additional brightness when charging. Irrelevant for this thead. Choose your favorite setting
• 5/7: Same of 4/7
• 6/7: Choose enable: That enable the app
• 7/7: Some additional notes: Press Done
Now important settings: go to Menu > Settings > General: Settings Mode > Advanced
Service Activation settings:
• Disable system handler > ON: When you use Power saving mode, you surely noted screen flicker, which is very annoying, and make unusable power saving mode. By set this ON: Android doesn't set screen too dim; instead Velis have a minimum of brightness set by Wizard 2/7. (Surely you find out that you avoid screen flicker, by setting autobrightness off and slider in 8-10%)
Sensors settings:
• Screen-on sensor value override: Set this value to 30000. Read below this post if you want technical explanation of this setting
After you establish these settings, you'll be able to unlock your phone all the time!
This is the trick: When you unlock your phone, you'll note that the screen is very bright (because Screen-on to 30000) and quickly adjust to the environment light. The failure is that electrical current to screen is defective, and when exterior light is dark, the screen make a dim effect and doesn't light up.
Note to Marshmallow users:
• This app make use of Screen overlay permisions: And marshmallow is very restrict with this kind of app. This is specially true when you are installing an app. All you have to do is deactivate the app in notification screen: press "OFF" button, adjust system brightness upper enough to not flicker the screen, install your app, and activate Velis Autobrightness again
• Because of Doze mode, wake up from this mode may avoid your screen light up, the first time you use your phone. Let 10-15 seconds your phone wake up, lock again, and unlock again, and velis will make its work!
I hope this post make your smartphone usable. I barely apply this trick to two phones, but I think this is a good workaround!
I used this app & the flickering is still available
What worked for me is downgrading the firmware on my g900f all the way back to Android 4.0. My phone came with version 5.0 and I noticed the problem only after I kept installing samsung's system updates. Will report if the problem starts up again but I'm running rooted and running nougat just fine so I don't see a reason to keep upgrading the firmware.
Edit: nevermind, this didn't work
Reyse said:
The technical explanation of this problem is: Screen doesn't receive enough electrical current at low brightness levels (maybe the flex is defective, get old, etc)
Click to expand...
Click to collapse
Does anyone know for sure if it's the flex cable or some capacitors? I notice only the lower half of my screen flickers.. I bet there's a simple electrical fix for it instead of replacing the whoooole display
fbs said:
Does anyone know for sure if it's the flex cable or some capacitors? I notice only the lower half of my screen flickers.. I bet there's a simple electrical fix for it instead of replacing the whoooole display
Click to expand...
Click to collapse
Hello,
Have you change jour battery? If it s old it could cause some issues...
But try to buy a genuine one, I think that your battery must be old now.
Bye
cedouic said:
Hello,
Have you change jour battery? If it s old it could cause some issues...
But try to buy a genuine one, I think that your battery must be old now.
Bye
Click to expand...
Click to collapse
it doesn't make any sense. the lower half of the screen flickers in green even on charger
fbs said:
it doesn't make any sense. the lower half of the screen flickers in green even on charger
Click to expand...
Click to collapse
I noticed that screen only flickers at low brightness when using Boeffla kernel for LOS14 and others based on it.
No issue for the same device with LOS or Stock based kernels.
zlazaar said:
I noticed that screen only flickers at low brightness when using Boeffla kernel for LOS14 and others based on it.
No issue for the same device with LOS or Stock based kernels.
Click to expand...
Click to collapse
you're wrong
I was using los16 with stock kernel for months with flicker everyday
fbs said:
you're wrong
I was using los16 with stock kernel for months with flicker everyday
Click to expand...
Click to collapse
+1 to that , i even went back to stock and the screen flicker appeared and such issues are well known already with samsung amoled panels back in 2014-even some panels from 2018 . So def not kernel related.
I was using los 15.1 and this problem got worse. The phone was barely usable as mentioned by the op. In my case, the screen would start flickering below 60%. Then I switched back to stock marshmallow. I noticed that 100% brightness in los 15.1 is actually only about 70% in the stock rom.
I have been using the phone at 80% brightness for some weeks now and the problem has significantly reduced. But not completely gone, it's much much better. Also, you might want to avoid using dark wallpapers.