Related
do you guys know how to or what apps can change the auto adjust level? and please dont say just manually change it, i like to use the auto feature, its there so i can be lazy.
Settings > display > brightness
Sent from my SGH-T989
You can go to settings> display> brightness and set it to auto brightness, or you can get the app "Quick Settings" it has a bunch of toggles
Sent from my SGH-T989 using Tapatalk
I think the OP wants something similar to what's in Cyanogen roms. I think he wants to adjust how bright or dim it gets on certain light conditions. I think I saw an app called Luminous or something. Now I'm drawing a blank.
Sistum Id said:
I think the OP wants something similar to what's in Cyanogen roms. I think he wants to adjust how bright or dim it gets on certain light conditions. I think I saw an app called Luminous or something. Now I'm drawing a blank.
Click to expand...
Click to collapse
I'm looking for something like this also.
I'm just sayin!
Sistum Id said:
I think the OP wants something similar to what's in Cyanogen roms. I think he wants to adjust how bright or dim it gets on certain light conditions. I think I saw an app called Luminous or something. Now I'm drawing a blank.
Click to expand...
Click to collapse
yea...thanks
http://android.modaco.com/topic/341706-custom-autobrightness-values-cm7/
Maybe if you found the file that holds the values, you could pull and push the file till you find what you like?
EDIT:
Try this, maybe this will work. I think this is what I saw once.
Lux Auto Brightness
https://market.android.com/details?id=com.vito.lux&hl=en
I think I might give it a try later on.
Juice defender has an option to set the brightness all the way from -80% to +150%. So autobrightness would have a larger (or smaller, if you prefer) range.
Sistum Id said:
http://android.modaco.com/topic/341706-custom-autobrightness-values-cm7/
Maybe if you found the file that holds the values, you could pull and push the file till you find what you like?
EDIT:
Try this, maybe this will work. I think this is what I saw once.
Lux Auto Brightness
https://market.android.com/details?id=com.vito.lux&hl=en
I think I might give it a try later on.
Click to expand...
Click to collapse
Have it. Recommend it. Slick app from a great responsive developer.
just use the notification bar
Hey guys
I found out that if you tap the notification bar on the top and slide your finger left or right, you can adjust brightness as you like. I think that is the easiest and quickest tip I found on this forum. not sure where I found it.. hope that helps..
^^ only works if the brightness toggle is off.. Awesome feature on sammys..
.
.
Galaxy S2 on TapaTalk
There is an app i am using that allows you to adjust the levels that the auto brightness use.
Called: LogGraph
it gives you a graph divided by roughly 12 steps of the brightness sensor so 0-12.
you can set the brightness level at each step the default (which i am using) is roughly:
Sensor% - Brightness level%
0-0
10-5
20-10
30-15
40-20
50-25
60-30
70-40
80-60
90-80
100-100
PMG 705 said:
^^ only works if the brightness toggle is off.. Awesome feature on sammys..
.
.
Galaxy S2 on TapaTalk
Click to expand...
Click to collapse
Thanks I was wondering why it didn't work.
Sent from my Hercules using XDA App
Reviving a slightly older thread here for some feedback.
Lux is a great and well designed app; I've been having issues with it - it doesn't seem to sample from the sensor (light or camera) when it wakes up, even though that is how I set it. I sent an e-mail to the developer, so hoping he can help me out. I also found it hard to understand the "levels" both in basic mode, and the lux/luma in advanced mode. I came from Cyanogenmod (on an Evo 4g) so I understand how the sensor works, but for some reason, whether it be the GS2 or Lux, the sensor does not seem to pick up a lot of variation in ambient light. I can cover up the sensor with my finger and the value that is getting doesn't seem to go below 2.
So I'm still struggling to get the auto-brightness (with an app or with the factory algorithm) to work properly compared to what I was able to get on my Evo 4g w/ Cyanogenmod (which was perfect by the way - once I have it all set up, absolutely perfect auto-brightness).
Actually I edited the framework-res.apk file and that did the trick. I tried lux before but it still didn't work like the default auto brightness.
I'm just sayin!
princeasi said:
Actually I edited the framework-res.apk file and that did the trick. I tried lux before but it still didn't work like the default auto brightness.
I'm just sayin!
Click to expand...
Click to collapse
I'm guessing this is something that can't be edited live or on the fly? It's got to be signed and flashed?
If that works, cool, but I'm totally hoping for an edit I can make live to system files from Root Explorer for instance.
davidemartindale said:
I'm guessing this is something that can't be edited live or on the fly? It's got to be signed and flashed?
If that works, cool, but I'm totally hoping for an edit I can make live to system files from Root Explorer for instance.
Click to expand...
Click to collapse
Yes, currently this is the only way to achieve this. Supercurio mentioned in one of his post earlier that he was working on an app that would allow us to make these type of adjustments.
I'm just sayin!
princeasi said:
Actually I edited the framework-res.apk file and that did the trick. I tried lux before but it still didn't work like the default auto brightness.
I'm just sayin!
Click to expand...
Click to collapse
I believe you that Lux doesn't work like the factory auto-adjust...no matter what an app. developer does, you can't replicate the responsiveness of what would be in the framework.
Could you explain further the edits you did and what it corrected? I am a software developer and I can figure out the basics, just was looking for an idea of what you edited in there and the specifics to get me going.
Thanks in advance!
onyx00 said:
I believe you that Lux doesn't work like the factory auto-adjust...no matter what an app. developer does, you can't replicate the responsiveness of what would be in the framework.
Could you explain further the edits you did and what it corrected? I am a software developer and I can figure out the basics, just was looking for an idea of what you edited in there and the specifics to get me going.
Thanks in advance!
Click to expand...
Click to collapse
I basically followed what they did here http://forum.xda-developers.com/showthread.php?t=1235212 to decompile the apk. I made adjustments to the value that represents the brightness under the lowest lighting conditions. I slightly increased the brightness under that value to help mask the blobs under low lit conditions. Hope this helps.
I'm just sayin!
princeasi said:
I basically followed what they did here http://forum.xda-developers.com/showthread.php?t=1235212 to decompile the apk. I made adjustments to the value that represents the brightness under the lowest lighting conditions. I slightly increased the brightness under that value to help mask the blobs under low lit conditions. Hope this helps.
I'm just sayin!
Click to expand...
Click to collapse
Yeah, saw that last night and just finished. Will probably need to dial in the values a bit to find what is optimal for me.
I'll post a Framework for others to use once I get mine all set. This is definitely the way to go for adjusting autobrightness.
Hello Everyone,
I have a problem with my amami and I doubt I am the only one but for some reason people do hardly complain: the brightness even at lowest possible setting is still too bright.
I had this back when I had original FW and I am having the same issue with CM11 (latest nightlies). Using manual control or auto-brightness doesn't make much difference, i.e. in a totally dark room the ambient light sensor reports 0Lux and the screen is still too bright.
I found a workaround already (the ScreenFilter app that people recommend all over the internet) but it sucks because it heavily reduces the picture quality, i.e. visibly reduces contrast and especially the gray color resolution. And it also doesn't reduce power consumption like real brightness value change would do.
I looked around for possible solutions and there is a trick with writting a new value of current limit to Linux settings (some mA value between 0 and 20 to some max_current file in procfs). And this really helps but also impacts the maximum brightness, the screen is hardly ready in sun light with reduced current.
Is there a silver bullet? I am thinking about writing an app for that but it would require SU permissions and is kinda dirty to implement. Can anyone recommend a better solution?
have you tried the xposed Modul "minimum brightness" ?
Install Lux Brightness. from play store.
You can overboost it or make the screen so dark that you can't even see it.
Another great screen mod is Twilight which basically dims the screen red based on clock so it helps fall sleep faster when using phone before bed.
New Folder said:
Install Lux Brightness. from play store.
Click to expand...
Click to collapse
Yes, another vote for Lux. It lets you set brightness to negative levels, mine is usually around -50%. https://play.google.com/store/apps/details?id=com.vito.lux&hl=en
Vote for Lux here too.
Nothing comes close
camaro322hp said:
Yes, another vote for Lux. It lets you set brightness to negative levels, mine is usually around -50%. https://play.google.com/store/apps/details?id=com.vito.lux&hl=en
Click to expand...
Click to collapse
Thanks for the hint. I tried the Lite version and AFAICS it simply uses the same trick as ScreenFilter and other "sub-zero" regulators, putting an alpha overlay on top of the image stack.
You can identify this kludge easily by looking at the button areas, they don't get darker anymore. And you can see the black level not getting real black, i.e. the power consumption is not reduced.
However, Lux seems to be one of the better toys because of the plugin interface. Unfortunately there is no HW plugin for Sony devices but judging by the quick look at the Nexus-4 plugin (it's open source!!) it should be possible to adopt this method to Z1 as well. So, maybe when someone could eventually implement that.
xposed Modul "minimum brightness" works, i tested it for you. you can make the screen dim to complete black with your normal display brightness slider without grey or black overlay. it just sets down the minimum brightness level to 1 or 0 (default is 10 or 20), so it should also work with enabled auto brightness
chertVdetali said:
I looked around for possible solutions and there is a trick with writting a new value of current limit to Linux settings (some mA value between 0 and 20 to some max_current file in procfs). And this really helps but also impacts the maximum brightness, the screen is hardly ready in sun light with reduced current.
Click to expand...
Click to collapse
As far as i remember, /proc is only used to call upon information, not to set specific values. What you are looking for is placed within /sys.
To be precise in /sys/devices/leds-qpnp-ee125e00/leds/wled:backlight/. There you will find a file called max_current with which you can easily control the brightness and set it to a very low level. Note that this actually dims the screen and not just applies a filter like most apps do...
One drawback is that the value will change again after you restarted the device. I set up a little flow with Automate β that takes care of this for me. I find this solution a lot better than all the screen filter apps.
This is true for CyanogenMod 11 and GreatDevs Kernel. It might be different on Stock. I know that the path for my Nexus 7 is sys/class/leds/lcd-backlight.
I hope this helps you a little bit.
rob rich said:
xposed Modul "minimum brightness" works, i tested it for you. you can make the screen dim to complete black with your normal display brightness slider without grey or black overlay. it just sets down the minimum brightness level to 1 or 0 (default is 10 or 20), so it should also work with enabled auto brightness
Click to expand...
Click to collapse
I am wondering how you can claim that the result is complete black. Calling this black is like saying "TN monitors have good black values" (I know such people, they change their mind quickly when they see my Eizo with a VA panel at night).
No, seriously, the default was already 10 (see config.xml in cm11 repo) and the difference between 1 and 10 is hardly visible. It's still way too bright for work without eye strain in the darkness.
@Wooaarr: thanks, this is apparently the way to go, I just need to find time to configure it. And yes, of course, the file is in sysfs and not procfs (automated typing, when I grew up with Linux there was no sysfs out there ).
chertVdetali said:
I am wondering how you can claim that the result is complete black. Calling this black is like saying "TN monitors have good black values" (I know such people, they change their mind quickly when they see my Eizo with a VA panel at night).
No, seriously, the default was already 10 (see config.xml in cm11 repo) and the difference between 1 and 10 is hardly visible. It's still way too bright for work without eye strain in the darkness.
@Wooaarr: thanks, this is apparently the way to go, I just need to find time to configure it. And yes, of course, the file is in sysfs and not procfs (automated typing, when I grew up with Linux there was no sysfs out there ).
Click to expand...
Click to collapse
when i disable autobrightness and push the slider to the left my screen goes completely off, so you wanna say that screen off isnt black? funny
chertVdetali said:
Thanks for the hint. I tried the Lite version and AFAICS it simply uses the same trick as ScreenFilter and other "sub-zero" regulators, putting an alpha overlay on top of the image stack.
You can identify this kludge easily by looking at the button areas, they don't get darker anymore. And you can see the black level not getting real black, i.e. the power consumption is not reduced.
However, Lux seems to be one of the better toys because of the plugin interface. Unfortunately there is no HW plugin for Sony devices but judging by the quick look at the Nexus-4 plugin (it's open source!!) it should be possible to adopt this method to Z1 as well. So, maybe when someone could eventually implement that.
Click to expand...
Click to collapse
Interesting information, I did not know that. You are correct, the navigation buttons are brighter than the rest of the screen at negative values. I had noticed that before but didn't know why. Works well enough for me though.
rob rich said:
when i disable autobrightness and push the slider to the left my screen goes completely off, so you wanna say that screen off isnt black? funny
Click to expand...
Click to collapse
Well, you claim that it works for me because you tested it on your device. So... yeah, why not, I could say what you mentioned above just following the same logics. :silly:
I'm using oneplus 3 official CM13
The screen is too yellowish and reddish
I like Oxygen OS screen color and white balance.
How to fix it??
도와달라 이기!!
just wait, your eye will adapt progressively.
The original OP3 color balance was like a TV in sport mode.
You can flash ElementalX Kernel for kcal http://forum.xda-developers.com/oneplus-3/development/kernel-elementalx-op3-0-01-t3404879. You'll need EXKM from Play Store tho.
Take a screenshot of your LiveDisplay settings and post it here.
proag said:
Take a screenshot of your LiveDisplay settings and post it here.
Click to expand...
Click to collapse
Color profile is normal and Display mode is off
Rhomoo said:
Color profile is normal and Display mode is off
Click to expand...
Click to collapse
Well, that's weird. Default colors should be just like colors on OOS.
You may wanna to play a bit with LiveDisplay settings and make it look good for you, plenty customization options out there.
Livedisplay is set to automatically change the colortemperature depending on daytime/sunset. You might want to find that setting and turn it off. Or wait for the next day ;P
Lownita said:
Livedisplay is set to automatically change the colortemperature depending on daytime/sunset. You might want to find that setting and turn it off. Or wait for the next day ;P
Click to expand...
Click to collapse
Aleady off...
I upgraded to Android Q DP1 yesterday through OTA and noticed the double-tap-to-check-phone feature now always displays the full lockscreen including wallpaper. Same thing for lift-to-check-phone. In Pie, it used to show ambient display first when double tapped. I have the Always On Display disabled. Is this a bug?
Settings
Display
Advanced
Lock screen display
It's there
Mr Patchy Patch said:
Settings
Display
Advanced
Lock screen display
It's there
Click to expand...
Click to collapse
Yes, the "Double-tap to check phone" and "Lift to check phone" options are still there, and when enabled those actions still wake the screen, but the wake behaviour has changed, which is what I'm wondering about. When woken, it now shows the full lock screen rather than the ambient display (black background and dark theme) that used to show up in Pie.
Shimakaze said:
Yes, the "Double-tap to check phone" and "Lift to check phone" options are still there, and when enabled those actions still wake the screen, but the wake behaviour has changed, which is what I'm wondering about. When woken, it now shows the full lock screen rather than the ambient display (black background and dark theme) that used to show up in Pie.
Click to expand...
Click to collapse
Ohhh...ok I know what you mean now. Personally, I like it the way it is now in Q.
Mr Patchy Patch said:
Ohhh...ok I know what you mean now. Personally, I like it the way it is now in Q.
Click to expand...
Click to collapse
It's down to personal preference for sure. I wish they would've made that wake behaviour configurable if it's not a bug.
I wish the same too even in full 10 release they didn't change this behaviour
It's better to wake the ambient display than to wale the whole phone in case you need to check nots.
:good:
Hey all!
I am glad too see somebody else also noticed it. I absolutely adore the clean design and funcionality of Pixel's AOD, but the changed funcionality of double-tap to wake (from waking AOD to waking the whole screen) annoys me. I even rolled back from Q beta to Pie hoping they would not implement this change in stable release. Now in order to see AOD you need to have it on constantly, which actually drains some 1% battery per hour (that actually makes it some 15-20 over a working day's period and is actually quite substantial.), also during the night. I also don't stare at the phone all the time to need AOD all that time - a gentle tap to peek the time, weather and notifications is just enough - I see some of you would agree.
Is there any way we can appeal to Google similar to OnePlus's feedback section?
Hey, has it also become iOS like?
I hate whole iOS lock screen turning on. What a shame
I spent time factory resetting my phone thinking that the missing ambient display settings were a bug, I never thought Google would remove that functionality. The language under the "Lock Screen Settings" sounds similar, but they don't do the same thing since now it just wakes the entire screen. Real bummer that Google keeps removing features.
Yeah, it seem they went almost full iOS on this And it was so good: tap twice - AOD shows, tap twice again on that AOD - the lock screen shows. Why Google, why! At least give us an option to schedule when the AOD can be turned off automatically (like at some hours at night).
And to think I bought the Pixel just a week ago to finally taste the stock Android. It is good, no doubt here (and the phone size and general style is very refreshing from thos behemoths I used from Sammy, OP or Huawei), but OnePlus seems much more thoughtful and practicality-oriented. And what is the more important the pledges from the OnePlus community actually work quite often which I don't expect with Google somehow.
I'm fine with it. Not a big deal.
Sent from my Pixel 2 XL using Tapatalk
Besides the general low quality of this piece of software, here are some specific pains:
1. SafetyNet test fails (no root) - WTF? Can't use any of my work applications because of that.
2. Status bar notification icons don't appear (except for Gmail, for some reason)
3. About device shows there's an update available but I can't update because I'm not the "owner" of the device (there is only 1 user configured, no multiple users) - screenshot attached.
Please share your experience and whether or not you're seeing the same issues (or more).
Thanks!
Another botched update from oneplus scams
Well, it's a good thing I decided that the OP9P would be my last OP smartphone. I'm gona stick with Pixel phone from now on. Finally release A12 and no phone or data works. Really OP???
- Phone stuck in 60hz like 99% of the time.
- Keyboard doesn't have this convenient padding anymore. (On botttom to make typing easier.)
- [Launcher] Can't search apps with a single up swipe anymore, will have to find some hacky solution again. Usually I put a KISS launcher shortcut on other phones. But why ruin it when they had it ....
- [Launcher] Folders open on the middle of screen. Makes no sensse.
- [Launcher] The whole launcher experience is just way worse.
- Battery Management is a mess, now there are other options per app. The previous settings were reset.
- Rooting with Canary Magsik can soft brick. Managed to fix it but it took me a while and I consider myself a veteran.
Honestly, tons of great features are missing. I wish they would just give us a lean AOSP instead like the ASUS Android and call it a day. This feels like a botched, budget Android on a cheap Chinese phone.
App drawers can only display 4 icons per row. Anyone knows how to change it to 5 per row or more?
it is no longer possible to film and in 21:9... or I am blind.
Like a say h8Aramex Phone stuck in 60hz like 99% of the time.
anhtin said:
App drawers can only display 4 icons per row. Anyone knows how to change it to 5 per row or more?
Click to expand...
Click to collapse
it's possible. settings --> home screen and lock screen
purpleman2k said:
Status bar notification icons don't appear (except for Gmail, for some reason)
Click to expand...
Click to collapse
That's not actually a bug, that's feature. Go to notification settings for particular app and you can set to show notification icon on status bar. Disabled by default for all apss (I think it should be enabled by default), except Gmail, Dialer and a few others.
Bug I found:
- font size issues. I want to set small fonts and dpi. But some apps, like default camera app, power menu, google feeds when swipe etc has still default large font, experience is terrible
- custom dpi set in developer settings will be reverted after reboot. If you set smaller dpi in phone settings, it will be applied a few seconds after boot, phone starts with default dpi
- AOD does not work, even if enabled, screen will turn off when inactive
I installed via built in ota from Oxygen 11 Global, I got update to ColorOS 12
Just got my first 1+ yesterday and was really impressed with the OOS 11 experience.
All day long. All the magic has gone after the update.
In addition to what was already said, the AOD is flickering terribly.
Perhaps it is caused by the pwm of low frequency.
Lol, I paid 1000 euros for this phone because the software was supposed to be good...
Oh yeah, the CLOCK. What is WRONG with that CLOCK!? LMAO.
I mean look at this ABOMINATION.
WHO DRAWS A CLOCK LIKE THAT? SATAN?!?!??!
Like wtf lol.
I have a new problem. I listen to music while walking with my wireless headphones. The phone is in my pocket. Unknown reason causes the phone to crash.
I feel it's going to be complicated.... At least I have 5G working.
Why would they remove the seconds on the clock feature. This update is horrible all around
anhtin said:
App drawers can only display 4 icons per row. Anyone knows how to change it to 5 per row or more?
Click to expand...
Click to collapse
Get Nova launcher and don't look back?
I'm not even going to upgrade A12, I deleted the 4gig update I got from Oxygen Updater. Oneplus just shoot them self in the foot and will not recover from this. I'll be suprise if they sell 1k Oneplus 10 phone next month.
h8Aramex said:
Oh yeah, the CLOCK. What is WRONG with that CLOCK!? LMAO.
I mean look at this ABOMINATION.
WHO DRAWS A CLOCK LIKE THAT? SATAN?!?!??!
Like wtf lol.
View attachment 5476711
Click to expand...
Click to collapse
Is your phone in 24-hour format? Mine looks normal in 12-hour format but like yours in 24-hour format. I don't use the stock clock app so I hadn't noticed.
ddizzy81 said:
Why would they remove the seconds on the clock feature. This update is horrible all around
Click to expand...
Click to collapse
They didn't. This is only when setting an alarm in the clock app.
Camera goes bananas when zoomed beyond 10x.. See attached
Any custom DPI set in developer options is completely lost after reboot.
Reported by me multiple times and was also seen in previous phones/Android versions.
Hi all, i can't open the icon option in the Launcher and and in the settings too it simply crash and nothing. Anyone as an idea? I just wipe launcher data but nothing.
h8Aramex said:
- Phone stuck in 60hz like 99% of the time.
Click to expand...
Click to collapse
Did you select "High" refresh rate in settings? Mine is at 120hz the vast majority of the time.
I have issues with screen brightness not adjusting to low-light conditions. When setting my phone on my dash mount I have to manually adjust the screen brightness down or go blind, even in dark mode. Worked fine with Oxygen OS 11. Fairly disappointed with the overall quality of this update, and I usually love getting the shiny new OS version update.