Hey Everyone,
As has been mentioned many times in other threads:
1) The LCD is often the biggest battery drainer
2) The 'minimum' setting of the brightness setting is still needlessly bright.
It certainly can be pushed further down for dim/night/dark settings.
3) Certain apps "dim" the screen but are just changing the color, not the backlight. So while useful they still aren't helping your battery.
Following some tips from a different android phone, I found this file:
/sys/devices/platform_/nov_cabc.0/leds/lcd-backlight/brightness
Which appears to contain the current 'brightness #' of the LCD backlight.
Using the normal Brightness slider, the value changes from 30 - 255, with 255 being the brightest. So this clearly could be reduced further.
Setting 'Screen Filter' to 50% brightness has no effect on the value.
Here's something interesting:
Assume the screen is already set at lowest brightness.
When I use 'Widgetsoid' to set brightness to '1', the screen dims slightly, then brightens back up. The 'brightness' file gets set to 20.
'widgetsoid 20' feels the same as 'min brightness 30'. - I wonder if Android is enforcing minimum backlight?
Anyway, thought that would be interesting to note. I'm going to download some other screen dimmer apps and see what they do.
- Frank
I found this online which is very interesting reading:
http://www.scribd.com/doc/35972886/An-Analysis-of-Power-Consumption-in-a-Smart-Phone
At '30' they said the display consumed 7.8 mW, while at 255 it consumed 414 (!!!)
Various apps coud push the value to 20 - tasker, adjbrightness.
Tasker tries to set it lower but as with widgetsoid, you can see the screen get forced back up to 20.
adjbrightness can "set" it lower than 20, but the entire screen blacks out, even at 19. Remember where the other buttons are so you can restore brightness!
- Frank
Whoa, thanks for the information. That pretty insane but its an apparently in the Market: Screen Filter, saves a helluva lot of battery.
Edit: Nevermind, Frank shut me up LOL.
Sent from my HTC Glacier using XDA App
I read a thread that said that the stock rom just doesn't allow setting it that low.
Ah well
- Frank
ChodTheWacko said:
I read a thread that said that the stock rom just doesn't allow setting it that low.
Ah well
- Frank
Click to expand...
Click to collapse
Can you set it lower in other roms - like cm7?
netter123 said:
Can you set it lower in other roms - like cm7?
Click to expand...
Click to collapse
I've been playing with CM7 which has some nice features for customizing the auto-brightness settings as well as the "dim" value which seems to be the lowest value the screen will go to and what it gets set to when the screen dims before shutting off after a timeout.
For the Dim setting in CM7, the default is 20. The next highest setting in the picker is 18. I believe it goes down to 0 or 1. When set to 18 or lower the screen blanks out completely when dimmed. Depending on how you test this, you may have a problem getting the screen back, so be careful you know where your widget button is on the screen to bring it back... 20 seems to be the lowest value. However, while dim, in a very dark room it could certainly be even dimmer so I don't know why lower values don't work.
I've also found the light detector doesn't seem to detect a continuum of light levels. It seems to be quantized at particular values, so there's a pretty hard limit on how fine you can set the auto brightness levels since the lowest light reading it seems to take is not very sensitive. It can't seem to distinguish between a fully darkened room and a dimly lit room, so setting the lowest value automatically makes the screen too dark to be comfortable in many environments, but then too bright for a really dark room. I don't know if this is an issue with the ROM software or a hardware limitation of the sensor. I've set my lowest auto setting to 40 which seems to work well, then I manually switch it to the dim value (20) if I'm in the dark.
I customized a luminosity curve for my surface rt, just edit the registry keys.
Download extract and run the attached .reg file and confirm the insertion of the Keys, then reboot the system.
Alert to make a backup of the old keys if you want to restore the previous state.
This change is compatible with all windows 8 but I have tested only on the surface.
Adaptive brightness varies proportionally to the user manual brightness, I suggest to manually adjust the brightness bar to about 20%, if you place the bar at 0 the brightness will be minimal with no automatic adaptation.
Appreciated thanks
New version v2
New improved version.
Try it and tell me if it's okay.
In the zip you will find the normal version and one with more brightness in the dark
I suggest to manually adjust the brightness bar to about 25%
So you have a fix, that's great. But to what? You didn't state what the problem is. Neither did you way what you are doing differently over the default values. Why would me, or anybody else for that matter, want do download this?
Amax said:
So you have a fix, that's great. But to what? You didn't state what the problem is. Neither did you way what you are doing differently over the default values. Why would me, or anybody else for that matter, want do download this?
Click to expand...
Click to collapse
In my surface the luminosity curve does not satisfy me.
The display seemed to have only three levels of brightness, setting an average value (ie on the desk in the room in the morning) adaptivity did not fit values for low-light (night) and lots of light, that is to say the brightness in the dark was not a minimum making it annoying for the view and unnecessary consumption of battery, instead with shaded light levels brightness became easily maximum, with again a waste of battery.
This forced me to move often the brightness bar manually, but now with my calibration does not touch more because it adapts automatically to any light condition.
Also the adaptation of brightness occurred after 3 seconds by the change of light, whereas now changes instantly in 0,1 seconds (100ms).
I like it a lot, just what I was looking for.
I use mostly in low light conditions my surface so it is very useful.
Just one remark: it is too sensitive so it is changing screen brightness very quickly even when I just touching the upper part of the screen and making a little shade on the light sensor...
So I think instead of 1 msec. would be better 3 msec.
Would you please and make a 3. version of the settings with 3 msec.?
Alapar said:
I like it a lot, just what I was looking for.
I use mostly in low light conditions my surface so it is very useful.
Just one remark: it is too sensitive so it is changing screen brightness very quickly even when I just touching the upper part of the screen and making a little shade on the light sensor...
So I think instead of 1 msec. would be better 3 msec.
Would you please and make a 3. version of the settings with 3 msec.?
Click to expand...
Click to collapse
100ms not 1ms! However, this file will change only the time in 300ms
antys86 said:
100ms not 1ms! However, this file will change only the time in 300ms
Click to expand...
Click to collapse
You are right, 100 ms. I was in a hurry. Thanks for the fast response and update
Your v2 seems to be working fine for me. Before applying it I could really tell when my surface was adjusting the screen, after applying it the transitions seems smoother and less abrupt.
I have been looking for documentation about how all of these things really work and the closest thing i could find was this link http://superuser.com/questions/644538/customize-adaptative-brightness-in-windows-8
but they seem to be using a different registry location than what you are and different registry names
regardless your settings seem to work immediately after restarting the sensor service
Hello,
Recently i upgraded my OnePlus 7 to OxygenOS 11 via OTA, and here is a list of a few annoying bugs(features?) that you'll need to know before upgrading:
(Note: I performed hard reset after upgrading, so any bugs here will be persistent and not because of some fixable issues, unless you are rooted/want to use adb maybe?)
(Also, this is the stock OOS 11, not rooted, and no modifications)
1) I'm not sure if it's just me, but the device heats up much faster. Though the temperatures here are high, I tried to maintain as close to a lab condition as possible, maintaining 30C ambient temp. Evaluation was done with a session of Call of Duty Mobile, and Youtube 4K video loopback test. Avg temps are: CODM : OOS 10: 41C, OOS 11: 45C, Youtube: OOS 10: 37C, OOS 11: 38C
2) Performance hit in games and frame drops (CODM, outside the ambient temperature maintained conditions), could be due to overheating? (As i mentioned, ambient temps are a bit high here). Also SystemUI lags sometimes. Adding to that, trying to bring up notification panel while playing a demanding game (like codm), the SystemUI (notification panel) opening animation is really choppy. (Is there some graphic driver issue?)
3) Brightness slider very slow to respond (seriously? Have to wait for 3 sec for the brightness to come up/go down on manually moving the slider)
4) Again, this one could be only me, but the audio seems to be a bit low after the update. All the ringtones and default notification sounds, with the same volume levels feels lower than how it was on OOS 10.
5) Battery drain - Device heat up and performance issues, translate to higher battery drain
6) This may not be a bug, but it's a change that i don't quite like (at least provide options?) : Double tap to wake doesn't give a vibration feedback like how it used to.
7) Everything, including UI and default font size is bigger than what I'm comfortable with (no, changing the font/display size doesn't give the expected results). But there's a workaround: Changing the display dpi from developer options from 384 to 420.
8) I had several app crashes (Instagram, Photos) even after disabling Android System Webview as suggested by some. But this issue seems to have been fixed magically for now.
9) This is a change, but to actually poweroff/reboot, you will need to reach your finger to the top of the screen with the new UI.
10) DC dimming has been removed
11) Weird QC issue-Someone thought any greyed out field in settings is because it's not supported by phone or HEADSET... Even in Private DNS settings.(See screenshot)
12) Natural colour calibration has a weird yellow tint (sRGB profile works fine tho)
13) Lots of missed/delayed notifications. Many times, notifications from apps like Instagram, Telegram doesn't arrive on time, with delays from 2 minutes to never arriving at all. Whatsapp seems to work most of the time. Sometimes, notifications don't make sound (weird), but only flash on the screen (Yes, I've verified all my notification settings, and I've set everything to make sound)
14) Now this might be a personal preference, but I don't quite like the way OxygenOS is trying to mimic OneUI (Huge heading and small contents beneath? Not my taste.) This style is followed in the phone, messaging, contacts, calculator, etcc
15) Quickly switching between recent apps, there's a split second of a black screen that appear before the app UI is displayed (not complaining, but this was not present in oos10, it seamlessly moved from the preview of the app on the recent apps screen to the actual app ui without any flickering, and no, this is not because of dc dimming being off or anything)
16) Google Play Music is still not removed (seriously, why still have it if it can't be used?)
17) FileDash - No longer has the DNS resolver for one.plus address. You will now have to manually type in the address displayed by filedash in your browser. Also, it still uses 2.4GHz and not 5GHz.
Edits: Added more bugs/missing features
Hem981,
I can confirm #7 is an issue on mine as well.
The power menu is an android 11 change not an OOS change.
I upgraded from OOS 10 to OOS 11 no wipe and don't seem to experience the other issues that you are having, except the obvious changes they made to the firmware. Have you tried clearing the dalvik-cache and rebooting? Mine was super buggy before doing this, but then again I just upgraded without wiping.
One issue I've personally noticed is the cell radios were a lot better on OOS 10, and I'm assuming that is the cause of the battery life to be worse.
Another that could be due to doing some debloating is when I take a screenshot and the little preview pops up in the bottom right corner if i click on it the UI will freeze after clicking back. The Nav buttons still work, like you can click on recents and the recent menu appears, back and home work but the screen is frozen otherwise until I force a reboot.
Yeah, I've tried factory reset and then wiping dalvik-cache... The performance was better before i performed the factory reset, i think. Anyway, there are quite a few games/apps where the performance impact is easily visible. Also, the power button thing is an Android change, but i really hoped OnePlus to have done something to make it more easily accessible (OOS is not pure Android). I couldn't find the issue with the cell radio you mentioned (as I've tried in areas in which i already had poor reception, and the performance was what was expected). Anyway, I really hope some of these (at least the performance, battery drain and the brightness slider issue) will be fixed soon over updates.
(For me, the SOT has gone down from 9.5 hours to 7 hours under similar use cases)
Yeah SOT has definitely taken a hit on mine as well, standby time seems the same. I also have noticed that the screen brightness needs to be set higher for the same brightness as OOS 10. The cell radio sometimes seem normal, but most of the time they are about 5-10 dBm higher at my house. I'll probably give a clean flash a try this weekend to see if it clears up.
One more issue found:
Weird red tint on screen auto dimming
The whole display has a weird red tint just before the device is about to lock/turn off screen after the timeout, when the display dims. It is easily noticeable if you have a white screen displayed. It only happens if you have set the brightness slider to anything other than the bare minimum (even a single step above the minimum brightness is able to replicate this issue)
I found something interesting: issue #3, the brightness slider being slow to respond to changes, seems to be fixed by disabling all animations from developer options. Should the window animator duration scale have any effect on the responsiveness/quickness of display brightness adjustment? I think that's stupid.
Also, I am starting to thing we need something like 0.1x duration scale for the animations (all animations on Android, or at least OOS), because honestly, with each new implementation, the animations are being too slow that it degrades the whole experience. 0.5x feels a bit better, but i really think something like 0.4x would match the animation speed of android 10.
You forgot to mention the vibration motor effect which has deteriorated since the update. The device now feels like any other cheap device.
It's kinda weird in my situation, just upgrading from 10.3.8 using an old version of xXx NoLimits to 11.0.0. The phone was super buggy when I first installed, but after rooting, wiping the delvik cache, debloating, removing the xXx module, and time to settle in the only issues I have are the screenshot popup, and the lower cell signal which I'm sure is causing a hit on battery life.
I was going to reinstall this past weekend, but for the time and inconvenience it's not worth the time compared to the minor issues I have.
Edit: Even the screen resolution seems normal now.
Again, don't know if this is an issue for anyone else (and i don't think OnePlus is going to change this): While everything else became bigger on the phone, the buttons/number keypad for typing in the screen lock pin became too small.
Hem981 said:
Hello,
Recently i upgraded my OnePlus 7 to OxygenOS 11 via OTA, and here is a list of a few annoying bugs(features?) that you'll need to know before upgrading:
(Note: I performed hard reset after upgrading, so any bugs here will be persistent and not because of some fixable issues, unless you are rooted/want to use adb maybe?)
(Also, this is the stock OOS 11, not rooted, and no modifications)
1) I'm not sure if it's just me, but the device heats up much faster. Though the temperatures here are high, I tried to maintain as close to a lab condition as possible, maintaining 30C ambient temp. Evaluation was done with a session of Call of Duty Mobile, and Youtube 4K video loopback test. Avg temps are: CODM : OOS 10: 41C, OOS 11: 45C, Youtube: OOS 10: 37C, OOS 11: 38C
2) Performance hit in games and frame drops (CODM, outside the ambient temperature maintained conditions), could be due to overheating? (As i mentioned, ambient temps are a bit high here). Also SystemUI lags sometimes. Adding to that, trying to bring up notification panel while playing a demanding game (like codm), the SystemUI (notification panel) opening animation is really choppy. (Is there some graphic driver issue?)
3) Brightness slider very slow to respond (seriously? Have to wait for 3 sec for the brightness to come up/go down on manually moving the slider)
4) Again, this one could be only me, but the audio seems to be a bit low after the update. All the ringtones and default notification sounds, with the same volume levels feels lower than how it was on OOS 10.
5) Battery drain - Device heat up and performance issues, translate to higher battery drain
6) This may not be a bug, but it's a change that i don't quite like (at least provide options?) : Double tap to wake doesn't give a vibration feedback like how it used to.
7) Everything, including UI and default font size is bigger than what I'm comfortable with (no, changing the font/display size doesn't give the expected results). But there's a workaround: Changing the display dpi from developer options from 384 to 420.
8) I had several app crashes (Instagram, Photos) even after disabling Android System Webview as suggested by some. But this issue seems to have been fixed magically for now.
9) This is a change, but to actually poweroff/reboot, you will need to reach your finger to the top of the screen with the new UI.
10) DC dimming has been removed
11) Weird QC issue-Someone thought any greyed out field in settings is because it's not supported by phone or HEADSET... Even in Private DNS settings.(See screenshot)
12) Natural colour calibration has a weird yellow tint (sRGB profile works fine tho)
13) Lots of missed/delayed notifications. Many times, notifications from apps like Instagram, Telegram doesn't arrive on time, with delays from 2 minutes to never arriving at all. Whatsapp seems to work most of the time. Sometimes, notifications don't make sound (weird), but only flash on the screen (Yes, I've verified all my notification settings, and I've set everything to make sound)
14) Now this might be a personal preference, but I don't quite like the way OxygenOS is trying to mimic OneUI (Huge heading and small contents beneath? Not my taste.) This style is followed in the phone, messaging, contacts, calculator, etcc
15) Quickly switching between recent apps, there's a split second of a black screen that appear before the app UI is displayed (not complaining, but this was not present in oos10, it seamlessly moved from the preview of the app on the recent apps screen to the actual app ui without any flickering, and no, this is not because of dc dimming being off or anything)
16) Google Play Music is still not removed (seriously, why still have it if it can't be used?)
17) FileDash - No longer has the DNS resolver for one.plus address. You will now have to manually type in the address displayed by filedash in your browser. Also, it still uses 2.4GHz and not 5GHz.
Edits: Added more bugs/missing features
Click to expand...
Click to collapse
Hi! Oneplus 7 ownere here.
Try to answer all the points:
1) i don't notice any difference between OOS10 and OOS10 on the heat of the phone
2) I don't know for the gaming performance but i don't play any games...overall, the performance are good, no system lags or freeze BUT I have the same issues with the notification...when i tap a notification, I often have delay, maybe it's just the animation but I remember the same issue on a Oneplus 8t that i tried for 20 days in last November
3) same issue here, very annoying
4) not just you, have same issue
5) battery drain is the same in my case, in standby maybe is less than before
6) me too, but maybe they change this as they planned?
7) yes, same thing. i changed the DPI from developer options too
8) no crashes here
9) this is an Android 11 change from Google, maybe they don't want your device to power off ahahah
10) never had this problem luckily
11) don't know, never tried this
12) i noticed this after reading this point, true on my device too
13) i faced the same issue on the notification sound, the other things works fine
14) me too, if i wanted One UI, i would have bought a Samsung...
15) sometimes happens to me, maybe it's bad ram management?
16) this is ridicolous, why they doesn't remove this app??
17) never tried
I also have an issue on the vibration. Now it's HORRIBLE, i have disabled because it's unusable
So, this is my question: change phone or rollback on android 10?
There's one more addition to the list: Always on display sometimes seems to override the notification lockscreen privacy settings. I have some notifications put as "view private content only when unlocked", but the notification contents are visible just when it arrives on the always on display (though it's content is hidden in the actual lockscreen)
I've reported almost all of these bugs, and hopefully we will see new updates fixing most of these.
Can someone on OOS 10 on OnePlus 7 confirm if the "style preferences" settings in sound settings is greyed out while the output is phone speakers (or no other sound output devices connected)?
New hotfix patch OTA rolling out now...
Here is what's fixed and what's not:
1,2 : Yet to test
3: Not fixed
4:Fixed
5: Yet to test
6: No changes
7: No changes(or not easily noticeable maybe?)
8: Not encountered any "ghost" app crashes yet
9: No change
10: DC Dimming is not back, so no change
11: Not fixed Is it that hard to remove 'headset' text from the UI?
12: Don't know if it's because my eyes adjusted to it, but it seems a bit better now
13: Not yet tested
14: What can I say?
15: Fixed
16: The ghost of Google Play Music still remains
17: Not fixed
Edits: Nothing much is fixed
Performance: Marginal improvements
SoT/Battery: Even worse. Getting almost half the SoT I got on OOS 10 under similar use case and network/tenperature conditions
Ghost app crashes reduced a lot (that might be the only fix) , but is not completely gone (saw that 1 or 2 times)
Haptics is still as bad as before
I'm just worried about this weired bug which has rendered my parallel whatsapp very difficult to use to share media. Any fix for this is highly appreciated - https://forums.oneplus.com/threads/whatsapp-media-problem.1411292/
Thanks and regards
OOS11 - Stable
I have no problems on my device until now (for games I dont know why I do not play)
I noticed, because I have tried both roms(beta4 & stable).Open Beta4 has better "battery management" than stable! Αs strange as it may seem but is a real for me..
Well yes .Battery drain higher than openbeta4
wifi works fine to 5ghz band & generally my device works quite well so far. Patience is needed and all problems will be fixed...
https://postimg.cc/gallery/YtQpVDm
After the recent OS 11 update ,the media in my device ( photos and videos) not being shown properly in Whatsapp. Some of the videos and pictures which I've already deleted in the gallery are appearing again only in whatsapp in unsupported file format.
I'll be glad if someone confirms that it's a bug in OOS 11.0.2 and that my phone is not the only one which is affected.
I'm using WhatsApp and Parallel Whatsapp. Also have setup a Work/Office profile on my phone.
Does anyone have any solution to this issue?
Thanks and regards!
For me, wifi no longer works. Whenever I try to enable it, it just immediately turns off. It also no longer recognizes my SIM card.
itdiestoday said:
For me, wifi no longer works. Whenever I try to enable it, it just immediately turns off. It also no longer recognizes my SIM card.
Click to expand...
Click to collapse
Try wiping cache from recovery
Update 11.0.1.1
I feel like this is a big joke.
Even more battery drain (yes, i did a factory reset).
Brightness slider issue still not fixed.
Performance still degraded (but i think there is a little bit of improvement)
Not sure about Wifi issues as i never had them.
Weird red tint on screen dimming
Still many ugly and inconsistent ui elements
Color profile is back to being broken (the yellow tint returned)
Update: I've started having the wifi disconnection issues, after 11.0.1.1 update. This is way too annoying.