Related
Hi all! I'm having some brightness issues on my Razr i and any help would be great!
I'm on stock 4.1.2 and was using Power Toggles brightness slider to change the brightness, but suddenly, with no changes on the phone, the brigthness level would change only after turning screen off/on. But the problem is not related to the app I think, because even auto brightness isn't working properly... I mean, when it has to get brighter, it works, but when it has to dim, again only if I turn off/on the screen.
Does anyone know what could be causing it?
Thanks in advance!
Sorry for the bad english.
luizlee86 said:
Hi all! I'm having some brightness issues on my Razr i and any help would be great!
I'm on stock 4.1.2 and was using Power Toggles brightness slider to change the brightness, but suddenly, with no changes on the phone, the brigthness level would change only after turning screen off/on. But the problem is not related to the app I think, because even auto brightness isn't working properly... I mean, when it has to get brighter, it works, but when it has to dim, again only if I turn off/on the screen.
Does anyone know what could be causing it?
Thanks in advance!
Sorry for the bad english.
Click to expand...
Click to collapse
Although you don't think the app is causing the brightness problem's I would recommend uninstalling it for troubleshooting purposes and seeing if after you have uninstalled the app and rebooted the phone if after some time the problem persists. This way we can rule out if the app is or isn't causing the problem.
shimp208 said:
Although you don't think the app is causing the brightness problem's I would recommend uninstalling it for troubleshooting purposes and seeing if after you have uninstalled the app and rebooted the phone if after some time the problem persists. This way we can rule out if the app is or isn't causing the problem.
Click to expand...
Click to collapse
Thanks for the reply. I did uninstall it and the problem remains... I installed volume slider (which has a brightness slider too) and the same happens: non "real time" brightness changing and the auto brightness still doesn't work properly... =/
luizlee86 said:
Thanks for the reply. I did uninstall it and the problem remains... I installed volume slider (which has a brightness slider too) and the same happens: non "real time" brightness changing and the auto brightness still doesn't work properly... =/
Click to expand...
Click to collapse
That is odd, I would recommend booting into recovery and performing a factory reset and then see if that fixes your problem.
shimp208 said:
That is odd, I would recommend booting into recovery and performing a factory reset and then see if that fixes your problem.
Click to expand...
Click to collapse
This is what I was afraid of... =/
I will just wait a little longer to see if anybody faced this issue before. I'm pretty sure a factory reset will do (since it started to act like this all of a sudden) but I want to find the cause so it won't happen again or, if it happens, I won't need to do a factory reset...
It's weird... what could make this issue appear? =/
luizlee86 said:
This is what I was afraid of... =/
I will just wait a little longer to see if anybody faced this issue before. I'm pretty sure a factory reset will do (since it started to act like this all of a sudden) but I want to find the cause so it won't happen again or, if it happens, I won't need to do a factory reset...
It's weird... what could make this issue appear? =/
Click to expand...
Click to collapse
One possible way of figuring out what is causing this issue to happen is to generate a logcat when you are adjusting the brightness settings and see if the log reports any background processes that are causing errors with the brightness control.
shimp208 said:
One possible way of figuring out what is causing this issue to happen is to generate a logcat when you are adjusting the brightness settings and see if the log reports any background processes that are causing errors with the brightness control.
Click to expand...
Click to collapse
Thanks for helping me!
I never generated a logcat before. So I installed CatLog from Store and generated a logcat doing the following:
1) Set brightness to auto
2) Put the phone under a lamp
3) Turned of all the lights: the brightness didn't change
4) Turned off and on the screen: when the screen turned on, the brightness was already on a lower level
The logcat is pretty messed... it shouldn't be like that right? =/
Is this helpful?
luizlee86 said:
Thanks for helping me!
I never generated a logcat before. So I installed CatLog from Store and generated a logcat doing the following:
1) Set brightness to auto
2) Put the phone under a lamp
3) Turned of all the lights: the brightness didn't change
4) Turned off and on the screen: when the screen turned on, the brightness was already on a lower level
The logcat is pretty messed... it shouldn't be like that right? =/
Is this helpful?
Click to expand...
Click to collapse
From looking at the logcat there is a lot of errors and warning messages with loading certain library files and Android runtime services that relate to power and screen brightness sensing. Another peculiar thing I noticed was that NFC seemed to be generating a couple error messages as well. Overall you were definitely right about it not being a normal log in this situation, I also like your testing methodology :good:.
shimp208 said:
From looking at the logcat there is a lot of errors and warning messages with loading certain library files and Android runtime services that relate to power and screen brightness sensing. Another peculiar thing I noticed was that NFC seemed to be generating a couple error messages as well. Overall you were definitely right about it not being a normal log in this situation, I also like your testing methodology :good:.
Click to expand...
Click to collapse
NFC is disabled... =/
Well, so any suggestion? Or just a factory reset would do?
luizlee86 said:
NFC is disabled... =/
Well, so any suggestion? Or just a factory reset would do?
Click to expand...
Click to collapse
Unfortunately a factory reset would probably be the best thing to do.
shimp208 said:
Unfortunately a factory reset would probably be the best thing to do.
Click to expand...
Click to collapse
Just wiped data through CWM and the autobrightness still doesn't work properly...when it has to get brighter, it gets, but when it has to dim, it doesn't...
luizlee86 said:
Just wiped data through CWM and the autobrightness still doesn't work properly...when it has to get brighter, it gets, but when it has to dim, it doesn't...
Click to expand...
Click to collapse
You could also try re-flashing the stock ROM to see if that fixes it, another suggestion that could possibly work is running a fix permissions utlity.
Reflashed stock rom and reinstalled all my apps. Everything was fine. Went to bed and woke up, the same problem with power toggles reappeared...
EDIT: found what was causing it! It is the latest version of Floating Notifications (when show on lockscreen is enabled)!
Thanks a lot shimp!
luizlee86 said:
Reflashed stock rom and reinstalled all my apps. Everything was fine. Went to bed and woke up, the same problem with power toggles reappeared...
Click to expand...
Click to collapse
That's wicked bizarre that even after all those things the problem still persists. You could try bringing it in to Verizon to see if they can do anything otherwise a hardware issue may have arisen.
Sent from my SCH-I535 using xda premium
Hello smart people! I just got the phone yesterday, super excited about the custom roms! My question the scrren keeps dimming while im using the device. It not only just dims but it acts like it tries to go to sleep, While im using it! It wont Reconize any touch, till i kinda wake it up. It does this multiple times a day. My brightness is set to auto, figured it might help with the battery drain, but other than that i'm not sure what setting I ticked to get it todo this.
BTW: I'm not rooted, nothing weird on this device, just apps
hatchetwarrior92882 said:
...It wont Reconize any touch, till i kinda wake it up. It does this multiple times a day. My brightness is set to auto, figured it might help with the battery drain, but other than that i'm not sure what setting I ticked to get it todo this.
BTW: I'm not rooted, nothing weird on this device, just apps
Click to expand...
Click to collapse
Auto brightness will definitely help with battery drain, but probably not in the way you're thinking. Pretty sure turning off auto brightness will help with the fading, but we'll need more info as far as diagnosing your lack of responsiveness to touch.
What (if any) case do you use/do you have a screen protector of some sort? Is it when you are outside in the freezing weather that you notice a lack of sensitivity in your touchscreen? Do you have any "battery saving" apps that you're currently running?
I didn't think about the battery saving apps causing this
Do you have Paypal installed? If so, uninstall it
Auto birghtness on LG phones is terrible. Try installing Lux Auto Brightness on the store, it's a lot better. Also, you can set your screen off time in the settings higher, it's probably set to stock of 30 seconds
Lux is what I use.
I'm new to greenify, so bear with me.
In the pro version, I enabled both shallow hibernation and aggressive doze, in addition to adding a number of apps manually.
However, I found that the proximity sensor became a bit wonky, waking the screen while still in a call, and occasionally failing to wake the screen on call end.
Is it possible that greenify is causing this, and if so, what would you suggest I change to fix it?
HTC 10 rooted, Xposed, Maximus HD (MM)
Sent from my HTC 10 using Tapatalk
BillTheCat said:
I'm new to greenify, so bear with me.
In the pro version, I enabled both shallow hibernation and aggressive doze, in addition to adding a number of apps manually.
However, I found that the proximity sensor became a bit wonky, waking the screen while still in a call, and occasionally failing to wake the screen on call end.
Is it possible that greenify is causing this, and if so, what would you suggest I change to fix it?
HTC 10 rooted, Xposed, Maximus HD (MM)
Click to expand...
Click to collapse
Absolutely! Disable aggressive doze and shallow hibernation as they generally offer no significant benefit on Android 6 (Marshmallow) and often trigger side effects similar to what you describe. I'd also remove ALL apps from Greenify's hibernation list unless they exhibit undesirable behavior.
Given MM based ROM be sure to enable 'Doze on the Go' in Greenify settings which will help your device enter doze more rapidly and remain there longer even when in motion.
Davey126 said:
Absolutely! Disable aggressive doze and shallow hibernation as they generally offer no significant benefit on Android 6 (Marshmallow) and often trigger side effects similar to what you describe. I'd also remove ALL apps from Greenify's hibernation list unless they exhibit undesirable behavior.
Given MM based ROM be sure to enable 'Doze on the Go' in Greenify settings which will help your device enter doze more rapidly and remain there longer even when in motion.
Click to expand...
Click to collapse
Done. Would you suggest a battery app to monitor wake locks, and if so, which one?
Also, a general question about lithium batteries should not be trickle-charged overnight, or left plugged in constantly because it stresses the battery. Just wondering if there's any truth to that, or if it's an urban legend.
Sent from my HTC 10 using Tapatalk
BillTheCat said:
Done. Would you suggest a battery app to monitor wake locks, and if so, which one?
Also, a general question about lithium batteries should not be trickle-charged overnight, or left plugged in constantly because it stresses the battery. Just wondering if there's any truth to that, or if it's an urban legend.
Click to expand...
Click to collapse
Not a fan of monitoring wakelocks which are broadly misunderstood and usually not the source of excess (operative word) battery drain. Android's native monitoring tools are generally adequate. Two well regarded alternatives are Better Battery Stats (BBS) and GSAM. Both can be found in the Play Store.
Leaving a Li-ion powered device on charge overnight is fine. Especially phones and other portable gizmos which are usually discharged the following day. However, Li-ion batteries should not be left in a fully charged or discharged state for an extended period as irrevocable damage can occur. That's why most Li-ion powered devices arrive partially charged which is the state they like best.
More detail: http://batteryuniversity.com
Davey126 said:
Not a fan of monitoring wakelocks which are broadly misunderstood and usually not the source of excess (operative word) battery drain. Android's native monitoring tools are generally adequate. Two well regarded alternatives are Better Battery Stats (BBS) and GSAM. Both can be found in the Play Store.
Leaving a Li-ion powered device on charge overnight is fine. Especially phones and other portable gizmos which are usually discharged the following day. However, Li-ion batteries should not be left in a fully charged or discharged state for an extended period as irrevocable damage can occur. That's why most Li-ion powered devices arrive partially charged which is the state they like best.
More detail: http://batteryuniversity.com
Click to expand...
Click to collapse
Thanks for that info. Very interesting site, but way above my pay grade. I guess by "extended period" that scenario would be a store demo unit that's constantly powered, or a home scenario of similar sort.
Here's what I took away from a brief overview, if anyone else is looking on:
(Sourced from 'How to Prolong Lithium Based Batteries' from Battery University)
From: Battery University:(emphasis mine)
Similar to a mechanical device that wears out faster with heavy use, the depth of discharge (DoD) determines the cycle count of the battery. The smaller the discharge (low DoD), the longer the battery will last. If at all possible, avoid full discharges and charge the battery more often between uses. Partial discharge on Li-ion is fine. There is no memory and the battery does not need periodic full discharge cycles to prolong life.
Environmental conditions, not cycling alone, govern the longevity of lithium-ion batteries. The worst situation is keeping a fully charged battery at elevated temperatures. [I'm reading this as a warning for those of us with quick charging cables]
The question is asked, “Should I disconnect my laptop from the power grid when not in use?” Under normal circumstances this should not be necessary because charging stops when the Li-ion battery is full. A topping charge is only applied when the battery voltage drops to a certain level. Most users do not remove the AC power, and this practice is safe.
Click to expand...
Click to collapse
Davey126 said:
Absolutely! Disable aggressive doze and shallow hibernation as they generally offer no significant benefit on Android 6 (Marshmallow) and often trigger side effects similar to what you describe. I'd also remove ALL apps from Greenify's hibernation list unless they exhibit undesirable behavior.
Given MM based ROM be sure to enable 'Doze on the Go' in Greenify settings which will help your device enter doze more rapidly and remain there longer even when in motion.
Click to expand...
Click to collapse
Still having some trouble from time to time with proximity sensor, screen wake (almost locks on or off) and fingerprint sensor when waking.
I wiped both dalvik/art and system cache which seemed to help for a bit and also seemed to make the phone a bit more responsive, but this afternoon, the above problems resurfaced.
Can you please recommend some settings to start with, since I'm a noob with greenify, and I'm not sure if I have everything set right. Also might app updates without a reboot have something to do with this?
HTC10
Maximus HD (MM)
Rooted (obviously)
Xposed
Thanks in advance!
Sent from my HTC 10 using Tapatalk
BillTheCat said:
Still having some trouble from time to time with proximity sensor, screen wake (almost locks on or off) and fingerprint sensor when waking.
I wiped both dalvik/art and system cache which seemed to help for a bit and also seemed to make the phone a bit more responsive, but this afternoon, the above problems resurfaced.
Can you please recommend some settings to start with, since I'm a noob with greenify, and I'm not sure if I have everything set right. Also might app updates without a reboot have something to do with this?
HTC10
Maximus HD (MM)
Rooted (obviously)
Xposed
Click to expand...
Click to collapse
With Aggressive and Shallow doze disabled the only other setting that might prove troublesome is 'doze on the go'. However, that one is important on MM as it prevents your device from waking and/or staying awake when in motion. Still, might be worth disabling to see if it makes a difference.
Rebooting after app updates is generally unnecessary unless recommended by the developer.
Additional thoughts:
- verify working mode is Root + Boost (Xposed)
- keep the list of apps to explicitly Greenify short (demonstrated bad actors); implicit doze will take care of the rest
While my preference leans towards Greenify (ease of use; flexibility; long term track record; community support) there are several other fine apps with similar functionality. Force Doze pops to the top of the list. Occationally a user will report issues with one while the other works fine. Another option to consider.
BillTheCat said:
Still having some trouble from time to time with proximity sensor, screen wake (almost locks on or off) and fingerprint sensor when waking.
I wiped both dalvik/art and system cache which seemed to help for a bit and also seemed to make the phone a bit more responsive, but this afternoon, the above problems resurfaced.
Can you please recommend some settings to start with, since I'm a noob with greenify, and I'm not sure if I have everything set right. Also might app updates without a reboot have something to do with this?
HTC10
Maximus HD (MM)
Rooted (obviously)
Xposed
Thanks in advance!
Sent from my HTC 10 using Tapatalk
Click to expand...
Click to collapse
If you have greenified any system apps, please reconsider. One of them may be the culprit.
If nothing else works, ungreenify everything and start from scratch. Greenify one app at a time, observing the behavior for some time before greenifying the next. You may find the culprit. Laborious, but effective.
Davey126 said:
With Aggressive and Shallow doze disabled the only other setting that might prove troublesome is 'doze on the go'...
Click to expand...
Click to collapse
tnsmani said:
If you have greenified any system apps, please reconsider. One of them may be the culprit...
Click to expand...
Click to collapse
Hey, guys. I'm still having trouble with both the proximity sensor and fingerprint sensor. Could really use some expert advice here.
The phone screen often does not come back on - especially during a long call or when switching between calls, and frequently just "loses its mind" and I have to press the power button to get the screen back, or even to turn the phone off. Another problem is waking via the fingerprint sensor which is unreliable.
I don't know if it's the settings I've selected (my money is on this one) or if there's a rogue app that's hosing me. For example, I use OneBox for my business IP Telephony. Could it be that?
I did, in fact, manually select a couple system apps to greenify, but that's because the ROM developer put them into the system space, rather than the user space. So I'm not sure if that counts.
Here's what I have so far...
Greenified:
ES File Exlorer Pro
Facebook
Firefox
Instagram
Key Ring
SensorPush
Settings:
Working Mode: Root+Boost
Shallow Hibernation DISABLED
Aggressive Doze DISABLED
Wake-up Tracking and Cutoff DISABLED
Automated Hibernation: SELECTED
Xposed based features:
Doze on the go: SELECTED
Wakeup Timer Coalescing SELECTED
Telephone Wakeup SELECTED
Greenifying System Apps: SELECTED
BillTheCat said:
Hey, guys. I'm still having trouble with both the proximity sensor and fingerprint sensor. Could really use some expert advice here.
The phone screen often does not come back on - especially during a long call or when switching between calls, and frequently just "loses its mind" and I have to press the power button to get the screen back, or even to turn the phone off. Another problem is waking via the fingerprint sensor which is unreliable.
I don't know if it's the settings I've selected (my money is on this one) or if there's a rogue app that's hosing me. For example, I use OneBox for my business IP Telephony. Could it be that?
I did, in fact, manually select a couple system apps to greenify, but that's because the ROM developer put them into the system space, rather than the user space. So I'm not sure if that counts.
Here's what I have so far...
Greenified:
ES File Exlorer Pro
Facebook
Firefox
Instagram
Key Ring
SensorPush
Settings:
Working Mode: Root+Boost
Shallow Hibernation DISABLED
Aggressive Doze DISABLED
Wake-up Tracking and Cutoff DISABLED
Automated Hibernation: SELECTED
Xposed based features:
Doze on the go: SELECTED
Wakeup Timer Coalescing SELECTED
Telephone Wakeup SELECTED
Greenifying System Apps: SELECTED
Click to expand...
Click to collapse
Did you try the earlier suggestion of removing everything from hibernation and then hibernating one app at a time? If not, try that.
What is SensorPush? Is that the wireless thermometer thingy? Disable that and see.
tnsmani said:
Did you try the earlier suggestion of removing everything from hibernation and then hibernating one app at a time? If not, try that.
What is SensorPush? Is that the wireless thermometer thingy? Disable that and see.
Click to expand...
Click to collapse
Actually, I figured I'd start from scratch. Disabled the app in Xposed, used TiBu to wipe data and uninstall. I'm going to wipe all the caches and reboot to see what happens.
What I could use some help with is to understand what settings in the app you guys would recommend for my phone /rom:
HTC10
Maximus HD (Marshmallow)
Xposed
Once I'm OK with basic settings, I'll follow your suggestion of one app at a tim.
Yes, Sensor Push is the app for remote temperature / humidity sensors. But it's not this app, I've only had it installed for a couple days, the problem has persisted for weeks beforehand.
Sent from my HTC 10 using Tapatalk
BillTheCat said:
Actually, I figured I'd start from scratch. Disabled the app in Xposed, used TiBu to wipe data and uninstall. I'm going to wipe all the caches and reboot to see what happens.
What I could use some help with is to understand what settings in the app you guys would recommend for my phone /rom:
HTC10
Maximus HD (Marshmallow)
Xposed
Once I'm OK with basic settings, I'll follow your suggestion of one app at a tim.
Yes, Sensor Push is the app for remote temperature / humidity sensors. But it's not this app, I've only had it installed for a couple days, the problem has persisted for weeks beforehand.
Sent from my HTC 10 using Tapatalk
Click to expand...
Click to collapse
No appwise recommendations can be made since the device, ROM, kernel, apps etc vary vastly not to speak of the the specific usage pattern of the individual.
What is recommended though is to greenify those apps which you don't use often but which keep running. Do not greenify apps which you often use.
As for system apps, be careful, but the same principle applies. Don't greenify something like PlayServices because its running is essential and it will continuously try to wake up draining battery.
Install BBS and monitor which apps drain battery and then greenify only those which drain but will not cause issues if greenified. Always greenify one app at a time to see the effects.
In general, greenify as less apps as possible.
I have a Moto G4 Play model number XT1600 (Moto G Paly in the US) and I am having some issues with the proximity sensor.
When answering a call, sometimes the screen goes dark and unresponsive to touch or by quickly pressing the power button. I have Greenify installed but I'm not sure if it is related.
After reading some posts here, I decided to understand the behavior of my phone when I make the calls and here is what I learned:
- after the proximity sensor turn the screen off when the phone is close to the ear, many times it will not detect when the phone is put away from the ear. But if you make a movement that leaves the phone in the horizontal position in your hand, the screen will be lit again (it takes a few seconds).
- if you put away the phone from the ear and leave it in a desk in the horizontal position, the screen will almost immediately be lit again. It seems that the proximity sensor works together with another sensor that detects the little bump when you put the phone on the desk.
- I did the movement to put the phone away from the ear, leaving it in the horizontal position in my hand; screen continued dark. Then with my finger I did a few taps in the back of the phone and the screen went on again.
- Another test I did when none of the above alternatives worked: in the settings there is an option to turn the camera on with a double press of the power button. When this option is set and the screen goes unresponsive while answering a call, I do the double click to activate the camera. The screen turns on with the camera app and then I am able to switch to the phone app.
Annoying but it is an alternative solution.
Not sure if this is the normal behavior but this is what I learned today
hjbuzzi said:
I have a Moto G4 Play model number XT1600 (Moto G Paly in the US) and I am having some issues with the proximity sensor.
When answering a call, sometimes the screen goes dark and unresponsive to touch or by quickly pressing the power button. I have Greenify installed but I'm not sure if it is related.
After reading some posts here, I decided to understand the behavior of my phone when I make the calls and here is what I learned:
- after the proximity sensor turn the screen off when the phone is close to the ear, many times it will not detect when the phone is put away from the ear. But if you make a movement that leaves the phone in the horizontal position in your hand, the screen will be lit again (it takes a few seconds).
- if you put away the phone from the ear and leave it in a desk in the horizontal position, the screen will almost immediately be lit again. It seems that the proximity sensor works together with another sensor that detects the little bump when you put the phone on the desk.
- I did the movement to put the phone away from the ear, leaving it in the horizontal position in my hand; screen continued dark. Then with my finger I did a few taps in the back of the phone and the screen went on again.
- Another test I did when none of the above alternatives worked: in the settings there is an option to turn the camera on with a double press of the power button. When this option is set and the screen goes unresponsive while answering a call, I do the double click to activate the camera. The screen turns on with the camera app and then I am able to switch to the phone app.
Annoying but it is an alternative solution.
Not sure if this is the normal behavior but this is what I learned today
Click to expand...
Click to collapse
I experienced this same issue on an older XT1030 which is the mini varient of a 2nd gen Moto X. Spent quite a bit of time trying to diagnose the issue (like you) and had devised various work-arounds that were never quite satiafsctory. Also rocking Greenify w/Xposed but ultimately determined that was not a direct factor with the proximity sensor glitch.
What fixed it (for me) was Gravity Screen which you can find in the Play Store. Takes a bit to get understand how to configure but very nice once everything is set up. One downside is you will probably want to disable Moto's active screen function - at least during initial configuration. Good luck.
Is there any reason why pending updates might have an effect on the proximity sensor?
Sent from my HTC 10 using Tapatalk
BillTheCat said:
Is there any reason why pending updates might have an effect on the proximity sensor?
Sent from my HTC 10 using Tapatalk
Click to expand...
Click to collapse
I have noticed that if app updates are kept pending in PlayStore, it does affect various things, which seem totally unconnected.
tnsmani said:
I have noticed that if app updates are kept pending in PlayStore, it does affect various things, which seem totally unconnected.
Click to expand...
Click to collapse
Ah. So I'm not hallucinating after all...
Sent from my HTC 10 using Tapatalk
Well guys, it looks like I'm going to have to abandon Greenify. I just can't seem to find any combination of settings that won't interfere with the proximity sensor. Unfortunate, really, because it's a great app and I even bought the donation package, but it's just making my life miserable.
Anyway suggests for alternatives would be appreciated. I have one mention for 'force doze'. Anything else?
Sent from my HTC 10 using Tapatalk
I wish I had more technical skills to understand why my Moto G4 Play (XT1600) had its proximity sensor behaving erratically for several days. I uninstalled Greenify and installed it again. Settings are
Working mode NON ROOT, Agressive doze ON, Wake-up Tracking DISABLED, Auto Hibernation OFF, Alternative Screen Off Mode OFF, Quick Action Notification OFF, Long Press OFF, Don't Remove Notifications ON, Xposed Features (not available), Greenifying System Apps OFF, Extras for Geek OFF.
My proximity sensor is working fine with Greenify installed.
I keep all my apps and system up to date and I suspect that some recent update may have fixed the erratic behavior of the proximity sensor.
hjbuzzi said:
I wish I had more technical skills to understand why my Moto G4 Play (XT1600) had its proximity sensor behaving erratically for several days. I uninstalled Greenify and installed it again. Settings are
Working mode NON ROOT, Agressive doze ON, Wake-up Tracking DISABLED, Auto Hibernation OFF, Alternative Screen Off Mode OFF, Quick Action Notification OFF, Long Press OFF, Don't Remove Notifications ON, Xposed Features (not available), Greenifying System Apps OFF, Extras for Geek OFF.
My proximity sensor is working fine with Greenify installed.
I keep all my apps and system up to date and I suspect that some recent update may have fixed the erratic behavior of the proximity sensor.
Click to expand...
Click to collapse
Aggressive doze is neither needed nor beneficial on most configs. However, it can result in erratic app/device behavior. Suggest disabling and observe drain over several charge/discharge cycles. If only looking at at sleep performance be sure to include 1-2 min after waking as the device plays 'catch-up'. If there are no overall benefits to aggressive doze why introduce the potential for side-effects?
Hi all,
This is my first Huawei phone. I noticed that brightness of the screen will reduce (darken) for some apps, eg fb, chrome, dialer, even the auto brightness is unchecked. Do you experience the same?
It's a feature to prolong battery, all Huawei phones has it.
gm007 said:
It's a feature to prolong battery, all Huawei phones has it.
Click to expand...
Click to collapse
Yeah ok, thanks.
How do I get rid of the "feature"?
It's making the phone completely rubbish to use.
If I turn "Auto brightness" ON, the phone adjusts the brightness according to the lighting conditions around it (the screen does NOT go dim when launching apps).
If I turn "Auto brightness" OFF, the phone DIMS the screen when launching apps.
Come on HUAWEI!!! If I want the screen to auto adjust, I will set it to auto adjust.
I turned off auto brightness, toggled brightness to max and used the chrome browser. The brightness remains constant. No issues for me.
ssang8888 said:
Hi all,
This is my first Huawei phone. I noticed that brightness of the screen will reduce (darken) for some apps, eg fb, chrome, dialer, even the auto brightness is unchecked. Do you experience the same?
Click to expand...
Click to collapse
After update today to Oreo:
Same Problem with Huawei Mate 9 Update MHA-L29 8.0.0.361(C431)
It's A BUG not a feature.
After rebooting it`s okay and after standby and on again same problem again!
With Android 7 no problem!!!
Hi,
I had the same problem. In developer options I had "Force GPU rendering" enabled and that caused the issue.
Just disable it. Reboot the phone and it should be ok. When it does not help, "Restore default settings" in the developer options and reboot again.
gabmac said:
Hi,
I had the same problem. In developer options I had "Force GPU rendering" enabled and that caused the issue.
Just disable it. Reboot the phone and it should be ok. When it does not help, "Restore default settings" in the developer options and reboot again.
Click to expand...
Click to collapse
No it's not working. I hqven't this option enabled, and if I open chrome it will dim a little.
I enabled GPU rendering and that sorted it thanks
Scrap that it's still doing it
Automatic Brightness Issues..
I have similar issue with the one wrote here in xda - https://forum.xda-developers.com/mate-10/help/brightness-automatically-reduced-apps-t3697589
That is even with the auto brightness ticked-off and smart screen feature also off, the screen will automatically dim after few seconds I opened the Facebook app for example.
I tried opening the Hi-Care app but it doesn't has this problem.
Can Huawei fix this very annoying bug soon?
I believe majority of users would not affected by this because they set their brightness less than 50%. But for those who prefer bright screen like me, this is extremely annoying feature even it said to help prolong battery life!
Thank you.
Would a custom ROM fix this issue ? Only reason I would root this phone ! Hopefully get one soon now that we have a custom recovery.
Can you try exempting from battery optimization? Search for "Configure Apps" in settings, go to special access, and then "Exempt from battery optimization"
I personally don't notice this issue, so I can't test it.
Try to disable "Increase Readability in Sunlight" at developer options
Same exact problem here on my Mate 10 Pro - first noticed it a couple days ago, after i had the phone for a day or two. It's a very slight change - I mainly notice it in Chrome and Facebook. Some apps do it, but not all. Basically, when you launch the app, the whites are normal brightness according to your set brightness, then within half a second, it dims just slightly - like 10-20%. Then if you press the home button, you can see a slight change again to normal brightness as the app fades out. Not the end of the world but still a bit annoying. I never noticed this with my Mate 9 (which didn't get Oreo yet). Would be nice to have a fix for this.
hrn85 said:
Try to disable "Increase Readability in Sunlight" at developer options
Click to expand...
Click to collapse
That's solved it :good:
marra2 said:
That's solved it :good:
Click to expand...
Click to collapse
Did you restart your phone or do anything after? i changed the setting and don't see a difference - seems like it still does it.
Just compared to my son's mate 10 Pro and his screen is actually brighter on the Facebook app and all our settings are the same so must be different panel.
ssang8888 said:
Hi all,
This is my first Huawei phone. I noticed that brightness of the screen will reduce (darken) for some apps, eg fb, chrome, dialer, even the auto brightness is unchecked. Do you experience the same?
Click to expand...
Click to collapse
Bro, Switch off everything in Setting>>Smart Assistance.
Make everything to off, surely it will help you.
The "adaptive brightness" is bugged and dims the screen on certain applications, regardless of what options you have turned on or off. Huawei confirmed it is an EMUI issue. Who knows if they'll actually resolve it as they don't see it as a major issue.
It was major enough for me that I sold my Huawei Mate 10 after a few days.
i dont have it in 8.0.0.137. bug was present in 8.0.0.128. atleast for me. there is maybe sligt dim for like 5% in music sometimes and thats it as far as i can tell
Same issue here, tried many different fixes and attempts to disable it, still happens in all apps/games. It is noticeable immediately once the app/game has been launched.
It feels like a 10-15% decrease in brightness. Hopefully this is fixed in the next update.
Ps. I previously had the Mate 9, had the very same problem!!!
The brightness keep slowly decrease until it hit zero when I'm in my room. It works fine in daylight. Also notice when I plug in my charger the brightness increase. I have battery saver disable. Do I have hardware issue or software.
Same!
Looks like a software thing. Some people are reporting it gets fixed if you disable Device Health Check Services; didn't work for me. Have tried adaptive brightness, adaptive battery and device health check enabled and disabled - no luck!
Let me know if anything else works for you.
HisFatness said:
Same!
Looks like a software thing. Some people are reporting it gets fixed if you disable Device Health Check Services; didn't work for me. Have tried adaptive brightness, adaptive battery and device health check enabled and disabled - no luck!
Let me know if anything else works for you.
Click to expand...
Click to collapse
How to disable the device health check service, first time hearing about this.
Aiden64 said:
How to disable the device health check service, first time hearing about this.
Click to expand...
Click to collapse
Open Settings app then search for health
I have same issue with auto brightness goes to 0 while in adaptive auto mode