My screen dims down when I open Settings app. I've tried add settings to excluded apps but it's not working.
Running Evolution X, A13, OnePlus 8T
Running Evolution X, A13, OnePlus 8T
[APP][2.2+] Velis auto brightness 5.00
- Thread starter velis74
- Start date
-
- Tags
- android brightness light screen
There was an Android version which introduced this "feature". Similar to lock screen ban VAB's getting. Unfortunately, at the time, I wasn't tracking this, so I don't know which android version, but Settings app is not accessible to VAB.
Thanks for the quick reply! Well that's a shame. That's Google being Google I suppose.
Well, I expect the reasoning was that they're protecting you from potentially malicious apps that would check battery in your stead
But more to the point, I suspect they were protecting connections and accounts this way. I don't really know, but I imagine I can see the reasoning behind this particular decision.Good news: I checked the option "Optional update system brightness setting" which have the description of being more estetiskt, but it's actually a great use case. This means that unless I go from a dark environment to a bright while in the settings app, the issue is solved!Well, I expect the reasoning was that they're protecting you from potentially malicious apps that would check battery in your stead
Before this , the settings app , as we know, had the manual brightness level and were annoying if you are in a bright environment with the manual brightness low or vice versa.
I dont wanna jinx it but I also wanna share if someone had the same issue.
Small request. Can you include the version number in the file name for the APK? Helps to make sure I have the latest version in a backup folder.
Thanks.
Thanks.
I have a feature idea. Automatis (or sheduled) brightness preset, amoled bright for the day, amoled dim for the night. Something like dark/light theme scheduler.
I'm trying to get an automatic build procedure working. Your request would be a side effect automatically taken care of. However, for some reason, right now the command line Gradle build fails for me while building from Android Studio doesn't.
Working on it...
This is currently taken care of with Tasker automation. I'm not entirely sure I want to start playing with schedules and other triggers. While we are developing an engine for stuff like this in the company, I didn't have an intent of using it in VAB. It woud complicate the settings even more.
Hi, I have opt in for beta and I'm still seeing v5.00 in playstore. Anything I did wrong?5.01 (23.1.2023)
- Fix an issue where settings would not activate transparent widget setting on purchase
- Fix for triple touch not accepting values higher than 3
- Fix for app not receiving notification of charger plugging in / disconnecting
Also, it seems one item fixed itself
- Fix: Configuration wizard crashes on screen rotate
Uploaded to Play store beta.
It would seem you have not. I have forgotten to promote 5.01 to production.
There were some plans for that. Do you know of any specific models that might have two light sensors?
This is really too many. There are only phones below 1000CNY（145USD） and many have only one photoreceptor, while phones above 2000CNY(290USD) basically have two photoreceptors.
For example,Redmi note10pro, released in June 2021, priced from 1499CNY, has front and rear photoreceptors.
Would it be possible to get around this limitation using root, as in by adding a root only feature to VAB to do it?
I am a long time user and I am used to VAB working system wide. The root only feature, if possible, would be greatly appreciated. Thanks for all the hard work.
If possible, that would be awesome. I feel when waking from lock screen, the brightness takes some time to adjust from dark to bright.
I honestly feel like this is a lot of effort for benefit to very few users in very limited scenarios.
I've literally never, ever noticed an issue with the lock screen.
If root is added, and as optional, what is the downside for user like you that don't have a problem?
Hello @velis74
First of all I want to thank you for a great app and a great job. It was my pleasure to pay to support your work.
I came across your app after I started having problems with the native adaptive brightness of my Xiaomi 13 (fuxi) yesterday. Two identical Xiaomi 13 phones, both same system version (stock eu rom, identical version), both measure the same luminance values (lux) in the control app, but both set the adaptive brightness differently if Auto brightness is on. It was driving me crazy. Especially since in lower light conditions that one phone set the brightness values so low every time that the display was almost unreadable and had to be manually increased. It started happening yesterday 6/7/2023 afternoon, maybe some system app update, I don't know... The only thing I found in the app installation history is the app update "com.xiaomi.discover version 23.05.18.756 6/7/2023 at 2:38 PM". Even restarting the phone doesn't help. However, I ask, is it not possible to influence the behavior of the native adaptive brightness of android in the phone, for example in the developer settings? E.g. by defining the lower limit of brightness, etc.?
Everything works perfectly with your app!
Thanks for the great work!
EDIT:
I will answer myself
Yes, it is possible.
The procedure that fixed the problem, step by step:
- Open the Settings app
- Go to Apps
- Tap See all apps
- Scroll through your app list and tap Device Health Services
- Select the Storage & cache option
- Tap the Manage space button
- Tap the Reset adaptive brightness button
- Select OK to save and confirm your choice
- The feature reverts to the factory default settings
Source: https://www.androidpolice.com/reset-adaptive-brightness-android/
First of all I want to thank you for a great app and a great job. It was my pleasure to pay to support your work.
I came across your app after I started having problems with the native adaptive brightness of my Xiaomi 13 (fuxi) yesterday. Two identical Xiaomi 13 phones, both same system version (stock eu rom, identical version), both measure the same luminance values (lux) in the control app, but both set the adaptive brightness differently if Auto brightness is on. It was driving me crazy. Especially since in lower light conditions that one phone set the brightness values so low every time that the display was almost unreadable and had to be manually increased. It started happening yesterday 6/7/2023 afternoon, maybe some system app update, I don't know... The only thing I found in the app installation history is the app update "com.xiaomi.discover version 23.05.18.756 6/7/2023 at 2:38 PM". Even restarting the phone doesn't help. However, I ask, is it not possible to influence the behavior of the native adaptive brightness of android in the phone, for example in the developer settings? E.g. by defining the lower limit of brightness, etc.?
Everything works perfectly with your app!
Thanks for the great work!
EDIT:
I will answer myself
Yes, it is possible.
The procedure that fixed the problem, step by step:
- Open the Settings app
- Go to Apps
- Tap See all apps
- Scroll through your app list and tap Device Health Services
- Select the Storage & cache option
- Tap the Manage space button
- Tap the Reset adaptive brightness button
- Select OK to save and confirm your choice
- The feature reverts to the factory default settings
Source: https://www.androidpolice.com/reset-adaptive-brightness-android/
Last edited:
I don't know of a way. If I did, root would have been added. I use it extensively in other projects.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
229[APP][2.2+] Velis auto brightness 4.84
A pretty powerfully adjustable auto-brightness app for your android device.
Notice: project is alive again. Latest app version is in Play store, one week later in full release.
Deployments from android 2.1 up. Latest versions development supports Android 5.0 and up.
Any feedback highly appreciated.
Beta testers (via Play Store beta program): just apply for beta.
The app features a developer settings dialog which can be reached by long-pressing proximity reading on main screen.
Google play link for download. (and description)
Manual
Looking to help with translations? Go here, register an account (if not registered already) and then click either "Join language" on existing language or "Suggest another language" if your language of choice is not yet in the project. Wait a bit for me to approve you and you can start translating.
lease note that the translation app is still an early WiP, so drop me an email to jure (at) velis.si if something doesn't work right for you or if you have a suggestion.
This app is translated to the following languages:
* English - base language
* Chinese by Jinran Lin
* Czech by Holly Hell
* Dutch by Maardiweb
* French by Pims83
* Italian by siggey
* German by Chef Koch
* Hungarian by XT69
* Japanese by Magus & Masaki
* Lithuanian by cukierkas
* Norvegian by MrMastodon
* Persian by Alireza Afkar
* Polish by trur3
* Romanian by rapttorx
* Russian by Pavel Utochkin
* Slovak by kubics
* Spanish by UnderXP
* Vietnamese by Vu Hien
* Slovene
Thank you all for your help. :highfive: VAB wouldn't be what it is without you!
XDA:DevDB Information
Velis Auto Brightness, App for the Android General
Contributors
velis74
Version Information
Status: Stable
Current Stable Version: 4.84
Stable Release Date: 2023-01-02
Current Beta Version: 5.00
Beta Release Date: 2023-01-05
Created 2013-11-12
Last Updated 2022-12-2312Thread reopened per moderator decision. Some of you already know there's a dispute with Lux auto brightness author regarding app description text. I have removed it in entirety to remove any ambiguity. Text on play store is in its 3rd revision which was written entirely from scratch. In my opinion it bears absolutely no resemblance to lux description.
Please do not comment on this in your further posts. The thread should remain on-topic.
If you still feel you have to say something about it, please PM me or the mod about it.
In the mean time I have released v 1.10.32
No more of no sensor reading (found out why service was crashing)
I have however detected an issue when the device is in a constant light conditions (night). Although I have the sensor reading, the graph still drops to 0 and minimizes the brightness.
Direct solution is to attempt to modify the graph and then cancel the operation. This will restore the brightness to the graph setting.
Edit: fixed
Edit: TO DO list updated and rearranged. Top items have high priority.
Thanks for all the support so far, everyone. I never hoped for such a positive feedback.
Jure10
Yeah, decided to give it anbother go. Not sure when I will find the time, though. Need to fix wizard which took some damage when I was doing support for the new Androids. Hopefully there will be something before THIS new year. :angel:10I think I found the cause of sensor readings getting stuck: it happens when you turn on the screen while proximity sensor is covered (active). The app then ignores the subsequent sensor readings because of proximity and when proximity is finally released, lack of further light events "causes" the app to not update the brightness according to most recent light reading. Of course, this mostly ever happens while in a dark room - that's when light events are very rare because the sensor just doesn't detect any changes in light.
I have added an auto-generated event to occur just after the proximity sensor should release so that the brightness will then be updated. In my testing, I cannot reproduce the problem any more.
I will upload the new apk to OP now and later today to the market. I just want to test a bit more because this isn't the only change I've done.10Sorry for no activity guys, I get so little comp time lately
I have however managed to make some progress and have updated first post with a new version that has the following new additions:
- Service will stop after a minute if auto brightness is disabled
- Support for proprietary sensor solutions on Sony Xperia, SGS2
- Updated translations: german, persian
This is not yet a release since I'd like to do two more things before I do that:
- Try to fix the graph freeze
- Create a first-start settings wizard
In order to do the first, this version (in the first post, not the market) contains some logging enhancements. I would ask someone with the problem to please drop me a mail with logcat @ level 9 (long press the proximity sensor reading values to set the level). All I need is a few seconds @ level 9 when the graph is not responding to light changes.
The second item will be a series of 4 - 5 dialogs asking the user about his basic preferences. I will make it so that even existing users will have the option of running this dialog.
Of course, I'm also interested in Xperia sensor support if any Xperia users are still following the thread. Maybe for the support to work correctly, apps like this will need to be active. The app should work even without that, but there may be some strange results because OS and app will fight for their brightness. Don't know what the OS does if an app sets its own brightness.
@shadowch: The baby is great, we're having so much fun. We already managed to get her to sleep during the nights (that's why I have no more comp time ) We're all going for a walk to lake Bled today.
