Good Day Everyone,
I have early stage Age-related macular degeneration. Right now, it is in the early stage, but I'm running into an issue with my OnePlus Nord N10 5G.
The center field of my eyesight is getting darker. For example of your phone is at the maximum brightness level, it would appears around something like 60% brightness to me.
So see a beautiful photo of an evening skyline, but I see a post sunset view. It's still there, I just see it darker.
Anyway, I really need to make my screen brighter then the factory set maximum level. Yes, I know that will effect my battery life l, but I simply need it.
The Google Store does have some Apps that "claim" that to do that, but the reviews always are always very mixed. Alot of the reviewers saying they don't work and they believe the app developers just want access to their phone data.
I have already gone to the "accessibility" section of "Settings". "High Contrast" and "Color Correction" have helped some, but not enough.
So after all that, my question is, dose anyone know of an app for the OnePlus Nord N10 5G that can legitimately increase the maximum screen brightness? In the alternative dose anyone know how trick the Android 11 (Red Velvet Cake) into increasing what the maximum brightness level is set at?
Jeff B
Hey @ARTEST4ECHO,
You maybe encountering the screen brightness/dimming problem that the OnePlus Nord N10 5G has. If you have noticed that occasionally the screen seems dimmer than usual, but the brightness control is turned all the way up then this might be the problem.
Unfortunately this is a super common issue with this phone. I'm very surprised no one else has replied yet. The Forum on Oneplus's website there is multiple threads about this issue with hundreds of people complaining. Unfortunately it seems that OnePlus either refuses or is unable to fix the issue!
There is one "workaround" that I have found that seems to work. At first it seemed to work every time but lately it's hit or miss. Which is very strange though because I never update my device, so I'm not sure why it used to work all the time and now it doesn't.
Here is that solution that someone posted on the OnePlus website forum. (Again it used to work every time until lately so your mileage may vary. Unfortunately this seems to be the only option that helps/resolves the issue temporarily, besides rebooting the phone. Oh in case you did not know if you turn the phone off and back on the issue goes away until it happens again... )
Temporary Fix How To:
How to temporarily readjust screen brightness when dimming issue occurs:
1. Swipe down from the top of the screen to bring up the notification bar and turn on automatic ambient lighting (the small sun icon with the letter "A" next to the brightness slider)
2. After turning on automatic ambient lighting, manually slide the brightness control up. (increase the brightness - it will still be low brightness even after doing that)
3. Then finally power down the phone screen and power it back up. (just short press the power button to power off the screen, then press it again to turn the screen back on)
4. The screen brightness should be back to normal. Then be sure to "disable" ambient brightness as mentioned in the first step.
Hopefully this solution will work for you. Unfortunately if it doesn't there's no other method that I'm aware of to resolve the issue. I've had the phone for now going on 2 years and have been searching for a solution to this problem ever since.
Related
I have Speed Rom 5.1 on my Amaze. When I am finished with a call, the screen stays black. I try to hit the power button, but nothing happens. I have to remove my battery in order to reboot. Can someone shed some light on why this happening? I am thinking that it may have something to do with my CPU Tuner settings, but I am not sure.
mrcash101 said:
I have Speed Rom 5.1 on my Amaze. When I am finished with a call, the screen stays black. I try to hit the power button, but nothing happens. I have to remove my battery in order to reboot. Can someone shed some light on why this happening? I am thinking that it may have something to do with my CPU Tuner settings, but I am not sure.
Click to expand...
Click to collapse
Probably that or a bad flash, just reflash, see if it solves the issue.
Most likely it's something simple, like an issue with your proximity sensor. I know there was an app that could calibrate that but I forgot what the app was.
Stock Rom - Black screen while phoning
There is a similar problem on my wife's phone with a stock rom (not rooted Amaze from T-Mobile). When making or accepting a call, the screen will instantly go off even without leaning the phone against anything and won't turn on unless the power button is pressed. Sometimes the screen would turn on by itself after a while after the other phone was hanged.
I've downloaded AndroSensor app: the proximity value does't change even when touching the area near the earpiece. It keeps showing ( 0.5mA ) 3.5 in.
I've found a thread which is there since april 2012 and describes quite a similar problem.
okay.. i just the original post date for this thread.. please don't bring back threads that are 6 month's old which issues might have been solved already since no ones been posting in it for 6 months...
(anyways) this is what i was gonna say
on my current s3 when my phone is placed to my ear it cuts off the display.. and if you pass your hand anywhere near the sensor's to the top near the camera it cuts off the display.. maybe there's a feature like that enabled on the stock rom also.. or you could possible check with the system settings to see "screen" on/off settings in display or power saving mode.. or something...
Thanks for the answer. I didn't notice that the thread was that old. I think I will keep up a newer one. But the current issue isn't likely to have been solved.
The problem doesn't seem to be triggered by wrong sensor measures (because the screen will go off even after disabling the sensor) nor does it depend on the rom version (same thing on the CM10).
Resolved:
It will sound stupid but I have found a simple solution:
I have just wiped the screen in the upper left corner where the proximity sensor is located and it started behaving normally. Though I don't use any protection tape on the screen it seem to have become less sensitive because of mud or sweat.
Dear all!
I am really in despair
I notice a strange phenomenon on my Galaxy S 3 (German version).
Sometimes there occurrs a flickering of the screen. It is caused by thin greyish horizontal lines which jitter with high frequency at some parts of the screen. You should not imagine it as some blinking of the whole screen. It's only a partial jittering of thin greyish lines.
It does appear at random, I cannot force this effect to occurr. Most of the times it's subtle, but sometimes it is clearly visible.
I read in some other threads that people noticed flickering in dependence of the power saving options. This I observed as well. But I don't know why. Unfortunately, none of the other threads came to a conclusion. And the problem seems to affect only very few devices.
My S3 was sent into repair twice. Two times the touch screen was exchanged. Last time they also changed "some electrical and mechanical parts". However, the flickering still occurrs.
I now tested for a while and made the following observations:
- it's not related to 3g, wifi or mobile connections in general (occurred while switched off)
- it's not related to "automatic brightness control" (occurred with manually set brightness, 1/3)
- it's not due to the display (they changed it two times)
- it's not related to ambient light (happened both with artificial light and in darkness)
- it's not related to the setting "adjust display color"
- neon light helps to trigger it, as well as switching the screen on or manually changing the brightness
- it's not related to any one of the single settings in "energy saving mode"
- flickering "survives" switching the screen off for a short time
- switching "energy saving" off always finishes the flickering
Can anyone shed light on the reasons for this?
Try unticking the second option in Power Saving mode, which is supposed to lower the FPS in order to preserve power. You can still user PS mode but the flickering should be gone.
iridaki said:
Try unticking the second option in Power Saving mode, which is supposed to lower the FPS in order to preserve power. You can still user PS mode but the flickering should be gone.
Click to expand...
Click to collapse
thank you!
i already unticked all single options there. didn't change it. the only solution is to switch the whole "enrgy saving mode" off as it seems.
paddybear79 said:
thank you!
i already unticked all single options there. didn't change it. the only solution is to switch the whole "enrgy saving mode" off as it seems.
Click to expand...
Click to collapse
I am sorry, I did not read the OP carefully enough, where you stated that
it's not related to any one of the single settings in "energy saving mode"
Click to expand...
Click to collapse
I am using PS mode with all the options checked all the time, I don't think I have ever disabled it, and I haven't noticed the issue you mention. Can you tell us more about root status/ROM/kernel on your device etc? Also, have you tried disabling PS mode and observing the phone for 24 hours or so, to see if it still does the flickering at some point?
I'm having same issue. As for the conditions my result is that it would only appear after wake up when power saving is on with lowest brightness. Also it's not noticeable on dark wallpapers. Any ideas other than "turn off" power saving mode?
Just to add, I'm running stock 4.1.2 version which didn't fix this problem and I was observing phone without PS for a few days without any flicker of this kind.
Hi, I bought new "Cubot Note S", what I discovered in the first use was "display whitish" lines lying vertically, when set to high brightness.
At first, I thought it was hardware problem, but later I observed, actually those white(ish) lines are present when:
- screen brightness is higher than about 70%
- and when display is showing darker colors (mainly for notification bar)
- or when using camera.
And also, when moving notification bar up and down, those "whitish" lines moves sideways!
I found one solution for this problem, with the help of "MiraVision" user mode settings, by altering "Color temperature, brightness, and contrast".
You can see the problem and solution in the VIDEO.
youtu.be/rVo6UCAJ96U
Questions:
1) Is it really software error, or hardware problem?
2) If it is a software problem, is there any stable custom rom for "Cubot Note S" ?
Thanks!
maqsudbek94 said:
Hi, I bought new "Cubot Note S", what I discovered in the first use was "display whitish" lines lying vertically, when set to high brightness.
At first, I thought it was hardware problem, but later I observed, actually those white(ish) lines are present when:
- screen brightness is higher than about 70%
- and when display is showing darker colors (mainly for notification bar)
- or when using camera.
And also, when moving notification bar up and down, those "whitish" lines moves sideways!
I found one solution for this problem, with the help of "MiraVision" user mode settings, by altering "Color temperature, brightness, and contrast".
You can see the problem and solution in the VIDEO.
youtu.be/rVo6UCAJ96U
Questions:
1) Is it really software error, or hardware problem?
2) If it is a software problem, is there any stable custom rom for "Cubot Note S" ?
Thanks!
Click to expand...
Click to collapse
Send the phone back to where you got it for a refund.
Many traits with the cubot note s include -
Doesn't boot up and hangs.
Boots up and the sim icon is missing.
Screen burn.
Boots up and sdcard missing.
Problems connecting to wifi.
The ota updater is dangerous and should never be used.
It has a couple of malware apps in system.
Volume button not working as it should.
There are also lots of pro's of course so it is worth £50, but only £50, no more than this.
Hi everyone, I've had my Moto Z for a couple of days now and am pretty happy with the device - even with the battery life I have one small problem, however.
Sometimes, when the screen is turned off, the Moto Display approach action won't work. In these cases, I also notice that the bottom right IR sensor isn't lit up - which it usually is when the display is turned off. The approach action only starts working again when I pick the phone up. This is very inconvenient and not how it's meant to be.
Is anyone else experiencing this bug?
At first I thought it might be an issue with Doze putting the process responsible for the Moto Actions to sleep, but after whitelisting all Moto apps the issue still sometimes occurs. I have not yet found out under which circumstances this happens.
Any help would be greatly appreciated!
EDIT: It seems this issue only occurs immediately after turning off the screen, after which there is a slight delay (a couple of seconds) before the IR sensor is activated. I will observe if this is really the case, which of course would render it a non-issue.
I purchased my S21 about 5 weeks ago and I am not sure if I have been experiencing this issue since I bought it but in the last week, I have noticed this issue. When my phone is locked, the AOD will either show for a few seconds to a minute or just won't show. I've ensured it is set to always show, power-saving not set to turn it off, no Bixby routines and any updates are installed for phone/AOD. I've even factory reset my phone and removed the case and screen protector and the issues are still persisting. Does anyone else experience this issue?
Disable all power management... it screws up all kinds of things.
Does AOD show if you tap the screen?
I have disabled all power management that I am aware of and still experiencing issues. I've set it to show on tap and while it worked the first time, subsequent taps do not show the AOD
Video demonstrating AOD tap to show issue
Sounds like a firmware glitch or the flash was corrupted.
Double check all AOD and screen lock settings.
Try turning AOD always on.
Try disabling screen lock... a lock out is the last thing you want anyway.
Play with it... Android's wuv attention.
The case or screen protector won't do this more than likely.
blackhawk said:
Sounds like a firmware glitch or the flash was corrupted.
Double check all AOD and screen lock settings.
Try turning AOD always on.
Try disabling screen lock... a lock out is the last thing you want anyway.
Play with it... Android's wuv attention.
The case or screen protector won't do this more than likely.
Click to expand...
Click to collapse
I normally use AOD always on, I'd tried the tap on the option to test. Going to try flashing it today to see if that helps despite the factory reset not helping.
So I've flashed the stock firmware back onto my device and the issues are still persisting. I've contacted support through the Samsung Members app and it's been escalated to the Research and Development team and am just waiting to hear back.
Did you update any Samsung apps after the reload before testing it? Go with the factory app loads.
Try disabling the lock screen... they tend to end up locking out the intended user anyway, sooner or latter.
If no one else is having this issue it very well maybe a hardware issue.
Did you ever wonder what happens when one or two micro transistor junctions out of the millions in a phone fail? Yes, well...
Unfortunately I can't recall if Samsung apps updated before I tested. I've already factory reset a few times so I'd rather avoid that for now. I've noticed the issues occur when using auto-brightness on AOD in lower light settings. When I say lower light, I mean in my study during the day which I never experienced issues with on my S20 FE. I've sent a report to Samsung Members and am waiting on them to come back to me.
The you
brodieb321 said:
Unfortunately I can't recall if Samsung apps updated before I tested. I've already factory reset a few times so I'd rather avoid that for now. I've noticed the issues occur when using auto-brightness on AOD in lower light settings. When I say lower light, I mean in my study during the day which I never experienced issues with on my S20 FE. I've sent a report to Samsung Members and am waiting on them to come back to me.
Click to expand...
Click to collapse
Did you ever get this fixed. I have the exact same issue on my s20 ultra
Edit: Nevermind just fixed it after 3 days troubleshooting. Oddly it was the the disable AOD while in power saving mode that needed to be disabled even though I don't use power saving mode. Samsung never seem to amaze me with these dumb persistent bugs.
Glad to see you solved the issue. I'd already confirmed this setting was off for me. It's still happening. Looks like it's something to do with the level of light detection as the issue only happens when I have auto brightness set for the AOD. The problem is it's not even that dark when it's happening and never occurred with my S20 FE.