yashsingh1/xdaforums huggingface dataset:
[Android Apps and Games] velis74:
Yes it would, but let me check if there's an api available to detect this windowed cover.
[Android Apps and Games] bieniu79:
Even if not, reading the proximity sensor should work good enough, because the closed cover well... covers the sensor. :)
[Android Apps and Games] Marx2:
Is there some tricks to lower power usage of velis ab? Some settings to for example less often read light sensor etc?
[Android Apps and Games] velis74:
the sensitivity section contains that, e.g. increase thresholds, decrease smoothing times. However, that will probably get you, say, 15% vs using a dimmer profile.
[Android Apps and Games] Marx2:
Why vab is more power hungry then system auto brightness? Does it use more sensors, or read them more often? Does it read sensors when screen is off?

While it's doesn't eat battery very fast, I'm surprised in statistics it's on the first place as application which uses cpu most.
[Android Apps and Games] velis74:
It is only power hungry if you're playing with it. It has a far more dynamic UI than system auto brightness. On my devices it doesn't even register...
[Android Apps and Games] ralpheboyo:
....i find it very minimal....
[Android Apps and Games] mchstream:
+1

---------- Post added at 03:53 PM ---------- Previous post was at 03:53 PM ----------

+1
[Android Apps and Games] Marx2:
I saw this behaviour too on my note 2. I was thinking my sensor is broken...
[Android Apps and Games] velis74:
I'm working on it. Unfortunately we have a couple weeks of rain forecasted here + my phone doesn't seem to be doing this. I'll need to get me one of the affected ones ;)
[Android Apps and Games] bornoxt:
Since I'm using the [MOD][XPOSED][N5] Ambient Light Sensor fix for Nexus 5 there is no more screen flickering (full dimm/full bright).

Maybe there is a solution in this module for you, [MENTION=2424510]velis74[/MENTION] !
[Android Apps and Games] velis74:
Hm, VAB already has the functionality mentioned in this module. Look for "Erratic sensor readings fix" in settings, at the end of "Sensors" section. I'm not sure it can catch exactly the scenatio mentioned in this module. It was developed for SGS 3 sensor which alternated between 0 and 10 lux readings, not 0 and 30000.
[Android Apps and Games] mchstream:
On my Nexus 5 without your app or when it is turned off the auto brightness works properly. Only when your app is on do I have this bright dim problem. In doors you app works excellent. In DIRECT sunlight is when it goes extreme bright to dark ( and vice versa ).

I will turn on the "erratic sensor readings" and will let you know if that corrects this problem.

Thank You.
[Android Apps and Games] velis74:
And the setting mentioned in my previous post doesn't help?
[Android Apps and Games] mchstream:
You replied too fast. lol.

Tried it with the erratic sensor reading setting on and tried it in the sun. Looks like its working great. Thank you.
[Android Apps and Games] bornoxt:
I've used your function a long time but sometimes there was although the switching between full bright/full dim but not as often as without.

IMO the Xposed module works better/smoother than the "Errating sensor fix".
[Android Apps and Games] mchstream:
FYI, I would rarely use the phone in direct sunlight, which is the only time I ever had the issue. Thank you for the quick easy fix.

btw, excellent app. used on three different phones and your app ALWAYS added several hours battery life to all my phones. With how I have my Nexus 5 setup, 4 days is my avg battery life. Thanks again!
[Android Apps and Games] velis74:
Actually, this is because I was conservative implementing it. My algorithm actually lets one occurrence happen before it blocks any further occurrences. This is because otherwise it would be less responsive in situations where the sensor worked fine as it would take 3 samples before the service would react.
[Android Apps and Games] sunsero:
The pinning feature in the notification used to be very useful but does not seem to work anymore.
[Android Apps and Games] velis74:
If you have automatic profile changing through llama, a profile change will "forget" any modifications to the current graph. Any graph modifications have to be manually saved if you want to keep them permanently. It seems I'll have to put this on my TODO list since lots of people have issues with the concept. Most feel that any changes to selected profile should automatically be saved. I intentionally don't mark profile as selected just because of this right now, but it seems it's not enough.
[Android Apps and Games] sunsero:
I think profile changing is not the reason here - the issue happens on the tablet where I have no profile changing via llama (except for an on "Screen off" event to reset to a low light profile).

What seems to happen is:

1. I set a (high) manual brightness level in the notification bar (without confirming or cancelling the change)

2. The light sensor gets covered and the brightness is drastically lowered.

3. The light sensor gets released and the (high) brightness level as set in #1 gets restored.

Btw, there's no proximity sensor in the tablet.
[Android Apps and Games] velis74:
This is intended: the change that you made will remain in effect until you first turn off the screen or until you cancel it through notification cancel button.
[Android Apps and Games] sunsero:
But as described in the steps above this doesn't work:

- In #1 the change is NOT cancelled.

- Between #1 and #2 the screen is NOT turned off.

- In #2 the brightness is adjusted by VAB anyway!

Or are we expecting different things from the manual adjustment? Is it so that just a point on the curve is adjusted while I expect that the brightness remains the same (i.e. is pinned) until I cancel the manual adjustment?
[Android Apps and Games] velis74:
Hm, this is how I understand this:

1. You set a custom brightness for some lux

2. You cover the sensor thus reducing the lux, screen brightness will go dimmer

3. You uncover the sensor, returning the lux to previous value

What you expect: the brightness should return to level before you modified it in #1. #2 should cancel the change from #1.

What the app does: the brightness is adjusted according to change in #1. Screen doesn't turn off, so the change remains in effect. It doesn't get cancelled just because in the mean time lux changed

Is this understandable?
[Android Apps and Games] sunsero:
No, I don't expect what you descibe I would expect ;)

I expect that the custom brightness that I set in #1 remains unchanged until the screen turns off or I cancel it - no matter what happens to the light sensor in #2 or #3. But VAB IMHO erratically adjusts the brightness in #2 and #3 even though I did not cancel my custom brightness and screen did not turn off.
[Android Apps and Games] velis74:
Ohhhhh

So you expect this:

In #1 you have set a custom brightness. You want this brightness to remain in effect no matter what happens with sensor readings?
[Android Apps and Games] sunsero:
Yes, that would be great! :cool:

It would make it possible to quickly set a temporary brightness if sensor readings due to frequent brightness changes become annoying.

Could you please make this behaviour optional or maybe add to the notification in addition to "Confirm" and "Cancel" also a "Pin" button?
[Android Apps and Games] velis74:
Yes, the pin button idea seems a good solution for this.
[Android Apps and Games] juuser:
Hi Velis,

I just love your app, but with Galaxy S5 i have a problem that after boot it starts up, but freezes all the other apps that should start on boot. Therefore screen stays on forever and power button also does nothing. If i manually disable/enable the app, after some time also other startup apps are loading and power button starts working again.

Is it possible to fix? Thank you:)
[Android Apps and Games] Pkt_Lnt:
Help [MENTION=2424510]velis74[/MENTION] help you. Post a logcat with full debug, please.
[Android Apps and Games] juuser:
Thanks! Sorry for stupid question but how to make a logcat:confused:
[Android Apps and Games] velis74:
I'm not sure a logcat would help me here, I'm afraid I'm not that good. It must be something with your phone as there are nearly 2K installs on this phone already. VAB itself doesn't do anything special on boot, it just starts the service as it would if you started the app from launcher.

Perhaps it's a combination with another app that does this?
[Android Apps and Games] Pkt_Lnt:
It might not help here, but it is an essential skill for XDA users for troubleshooting in the future.

http://xdaforums.com/showthread.php?p=28181474#post28181474
[Android Apps and Games] gaich:
[MENTION=2424510]velis74[/MENTION]

My friend asked to update Russian for this beautiful app - I do not know, whether supersmooth wizard translation is needed, because it isn`t present in Google doc translation files, but I included it as well. Everything else is updated to the latest version: View attachment 2743027
[Android Apps and Games] velis74:
I will include it. Please use values from gdrive next time as this creates extremely huge amount of work for me (manual copying all the relevant translations into the properly formatted values.xml).
[Android Apps and Games] sunsero:
When the pin button gets implemented could you please also add a locale action to pin a specifiable brightness and to release the pinned brightness as well?

e.g. Velis Pin brightness: brightness 0=unpin or specify brightness 1 to 255
[Android Apps and Games] pisasax:
brightness change continuosly when using keyboard...help!

Hi all!

I'm running the 3.10.137 version because it is very stable for my Zopo Zp980 (mtk6589T) with custom presets. If I upgrade this marvellous app to the latest version on G.Play, I have problem when using the keyboard: the brightness of the screen changes continuosly and I get irritating :mad:. Therefore I tried to change the smoothing time downwards values but without effect.

May I have your kind attention to solve this problem?

Thanx in advance!

EDIT: Maybe I found a solution by myself just increasing the smoothing time downwards from 25000 to 50000. Let's hope this will fix this marvellous app.
[Android Apps and Games] velis74:
Sorry about long time no hear, been very busy at work @ home. I'm developing skins for the app and it's taking way too long. That's also why I can't yet publish the greek and updated russian, really sorry about that. I'm nearly at the end though, so I hope to be able to publish at least a seemingly unchanged (internally the changes are HUGE) update soon.

I will look into it.

I don't know what you mean exactly by "contiuously", but I myself have detected fault in steadyscreen functionality. Despite a long setting, it will change screen brightness when typing. I will try to address this problem ASAP.
[Android Apps and Games] sunsero:
One question regarding super dimming: When there's no super dimming active is there still an overlay or is it removed?
[Android Apps and Games] velis74:
The overlay is there as it must be, only it's 1x1 pixels instead of whole screen and fully transparent.
[Android Apps and Games] pisasax:
Steadyscreen functionality is exactly the problem when typing. And, despite my attempt to change the smoothing time downwards from 25000 to 50000 the problem is still existing...:crying:
[Android Apps and Games] sunsero:
Sounds like there's technically no way to remove the overlay :confused: So when the overlay is smaller there's no issue with APK installer? Actually I've got some overlay apps that don't interfer with APK installer, e.g. Intelliscreen and Frontmost.
[Android Apps and Games] velis74:
No, as the overlay is used to set screen brightness.

I have not found a method that would work with full-screen overlay and installer. The installer simply checks if there's an overlay over the button and refuses to acknowledge any press to the button if that is the case. How those two programs do it (if they do it), I don't know.
[Android Apps and Games] sunsero:
Those programs are not doing a full screen overlay so that might why the APK installer works.
[Android Apps and Games] sunsero:
[MENTION=2424510]velis74[/MENTION]:

On my S3 mini I did another test: I set the screen-on-sensor-override to 255. When I turn on the display the screen is at first still very dark though 255 would be rather bright. When I'm quick enough to open VAB from the notification area, I can see however that the sensor value is at 255 and in the graph in the vertical red line is also at 255. So somehow the display just does not match the brightness shown in the graph at value 255.
[Android Apps and Games] velis74:
[MENTION=5221171]sunsero[/MENTION]: just a quick question: do you want the pin button because steadyscreen isn't really working or do you see any added value in the pin button *over* what steadyscreen already provides?
[Android Apps and Games] sunsero:
Whcih feature do you mean with "steadyscreen"?
[Android Apps and Games] velis74:
Screen touch in the sensors section.

I really need to organise settings better & update the manual. :( :p
[Android Apps and Games] sunsero:
Well, I'm not using this one because I expect the brightness won't adjust with that option if the environment light changes.
[Android Apps and Games] velis74:
Isn't that the idea with pin button?

Steadyscreen makes sure that brightness stays the same while you interact with the device.
[Android Apps and Games] sunsero:
Yeah, but I still have issues with the screen starting too dark after superdimming and I don't want the adjusting to take longer because of interacting with the device (e.g. unlocking).

Also sometimes I just want even more brightness than defined in the curve, therefore the request for the pin button.
[Android Apps and Games] velis74:
Aha, ok.

Just FYI, steadyscreen knows when device just woke and uses current brightness before locking.

Anyway, will see what can be done about pin. There will be an intermediate release tomorrow and after that i will take it on
[Android Apps and Games] velis74:
4.01.177 (4.6.2014)

New translation: greek by pugsang

FIX: steadyscreen functionality now much more stable

Uploaded to OP and play store beta.

[MENTION=3717678]pugsang[/MENTION]: sorry it took so long
[MENTION=4563466]gaich[/MENTION]: ditto, can you please check? There was some mixup in translations for the word "profile". I can read some cyrillic, so I tried to merge as best as I could, but am not sure if the result is OK.
[MENTION=5221171]sunsero[/MENTION]: the steadyscreen does have a triple-tap option where it will immediately adjust screen brightness if you triple-tap the screen
[MENTION=4582188]pisasax[/MENTION]: i have tested steadyscreen all of yesterday and didn't find any faults with it (any more). Please try and report any findings. My test settings: smoothing time 3sec, change sensitivity 5%, steadyscreen 10 seconds

Now to start on the other stuff. My TODO list is getting bigger than the feature list :p
[Android Apps and Games] kantjer:
Thanks mate.

Is my eyesight getting worse? I can't seem to find the beat on the OP ;)
[Android Apps and Games] velis74:
It doesn't allow uploading apk as image any more - or something failed when i tried. It's in the downloads section (pc browsers only i'm afraid)
[Android Apps and Games] kantjer:
Hadn't looked in the downloads section :o

Sorry for that.
[Android Apps and Games] gaich:
You have replaced "Профиль" with "Шаблон"? It would be good too.

I`ve got other questions:

View attachment 2779928

1) The app name is translated - do you prefer it to be?

2) One translated string is missing (<string name="current_brightness">Тек. яркость экрана</string>), as you can see in the picture above.

View attachment 2779929

3)There`s a mess with these strings:

<string name="System_brightness_handling_on">Включено системное управление подсветкой, что мешает работе этого приложения</string>

<string name="System_brightness_handling_off">Системное управление подсветкой выключено</string>

When the toggle is on, the description is opposite (for the off position) and viceversa.

4) And, replace, please this string, there`s enough place for a whole word:

<string name="System_handler">Системное управление</string>

5) There`s a mistype I found, sorry, please replace <string name="tasker_not_bought_desc">Условия и параметры tasker / locale являются платным контентом. Если хотите их использовать, перейдите в магазин и совершите покупку.\nСпасибо.</string>

Thank you.
[Android Apps and Games] velis74:
It wasn't me who replaced it, it was in the original translation.

1) it says in the XML to not translate that, but some still opt to do it. It makes no difference to me.

3) This is because of (4)

4) The original translation for this string is "Disable system handler", not "System handler" as current russian translation says. That's why those two strings in (3) seem to be reversed.

Can you please correct the translation?
[Android Apps and Games] gaich:
Yes, I have corrected all this: View attachment 2780204
[Android Apps and Games] gaich:
[MENTION=2424510]velis74[/MENTION]

Sorry, just found one more mistype in special symbols, this string should look as follows:

<string name="wizard_brightness">Насколько ярким Вы хотите видеть свой экран?

\n\nПредустановки яркости ниже расположены в порядке убывания яркости.

\nПожалуйста, выберите начальную предустановку.

\n

</string>

This is corrected XML: View attachment 2781515
[Android Apps and Games] velis74:
I have included it and published to beta. Should be available shortly.
[Android Apps and Games] Marx2:
I would like to have possibility to edit curve online.

Let's say there would be two buttons in info area: darker and lighter (or plus and minus).

I'm choosing some starting curve and using phone. At the moment i feel screen is to light i would pull down info area and press minus button. It would affect curve permanently as i would add point on it and lowered it. Same when screen is to dark - i would use plus button to move current brightness point on curve up.

I think this way i could end up with curve much better aligned for my needs. And i would change it immediately.
[Android Apps and Games] velis74:
???

you have two ways to do this currently:

1. In the graph, just move the horizontal handle a little up / down.

2. In the notification, adjust to your desired brightness and press the confirmation button

Or did i misunderstand what you wish to do?
[Android Apps and Games] gaich:
Everything seems to be correct now, but I have made minor fixes again, mostly for better look and style, please use this for the next update:View attachment 2782683
[Android Apps and Games] headhunter678:
Nice :)

Gesendet von meinem Nexus 4 mit Tapatalk
[Android Apps and Games] Marx2:
Ok, in notification area i see i can click and then i can move bar and confirm (in previous version it was always active). Is such change permanent? Does it change curve?
[Android Apps and Games] velis74:
Such change is permanent unless you change current profile (without saving current one)
[Android Apps and Games] pisasax:
HI Velis!

After a period of test I can realize that unfortunately the screen is not enough steady when typing. Occasionally it also flashes! Sorry...

Inviato dal mio ZP980 utilizzando Tapatalk
[Android Apps and Games] velis74:
Do you type very fast? more than three characters in 600ms?

What exactly does it mean "it also flashes"? As in literally flashing?
[Android Apps and Games] Marx2:
I suspect it makes screen dark-light very fast multiple times. Erratic read sensor setting sometimes doesn't help. My note 2 tells velis 0 lux while its bright around. It's probably bad sensor, or velis read value improperly.
[Android Apps and Games] pisasax:
Actually I don't type very fast and the screen literally increased to high brightness. Anyway this time I made a clean installation, then launched the wizard and adjusted the values and...everything seems to work perfectly. I'll let you know. So far so good...
[Android Apps and Games] velis74:
Note 2 has a sensor that's a bit faulty. However, you're the first to say that erratic sensor readings fix doesn't work.

Do you mean that sometimes it still flashes once before stabilising or that it simply doesn't work?
[Android Apps and Games] Marx2:
Yes but very rarely. Now bigger problem is with reporting 0 lux while its bright around. I don't know if it can be fixed via some settings in velis?
[Android Apps and Games] sunsero:
[MENTION=2424510]velis74[/MENTION]:

Just changed log level from 3 to 0 in developer support options. Could it be all the delay and performance issues I experienced were due to the log level? Seems currently quite faster now!
[Android Apps and Games] renatohm:
Will translate it to Portuguese - Brazilian ASAP!
[Android Apps and Games] cukierkas:
Hello velis, how are you?

Updated my phone to LG d605,but it has no lux sensor, so I decided to try camera readings. Working fine, but I've got another issue. No camera or flashlight or Bluetooth is working. Camera says it's already in use, bt just stops with error. Turned off velis, still the same. Uninstalled velis, still the same, can't use camera or Bluetooth. Can you help me sort it out?

Kitkat 4.4.2, rooted.

Regards.
[Android Apps and Games] Pkt_Lnt:
Try to clear cache and data in Camera - Settings > Apps > All > Camera
[Android Apps and Games] irc32:
very interesting application everyone should has this.
[Android Apps and Games] cukierkas:
Thanks for reply. But sadly that doesn't worked. At gallery, front camera made some shots, I've deleted them as well.

What else should I do more?
[Android Apps and Games] cukierkas:
My mistake fellas. Finally found the answer to cameras problem. Yesterday edited platform.xml to have acsess to memory card read/write. After update memory card works petfect, but camera cant login in to in. Reverted changes back and yes, camera works fine. Sorry for disturbing. Kitkat is so limited in some cases ?
[Android Apps and Games] renatohm:
Portuguese - Brazil translation

Sorry it took so long, been quite busy these days!

Translation to Portuguese - Brazil attached!
[Android Apps and Games] velis74:
Sorry about not replying guys, XDA didn't notify me about new forum posts. Happens sometimes.

This seems unlikely to be the cause. Log level 3 is quite sparse and logcat is a very trafficky thing in Android. VAB @ log 3 can't contribute more than a few percent to it. I will drop it to default to 0 though, it was useful in the early days when VAB was extremely buggy, but not so much nowadays.

Whew (wipes sweat). Glad to hear you resolved it. I wouldn't have much to suggest anyway since VAB only uses the camera through standard API, it doesn't "lock" it or anything except in the meaning that camera can only be used by one single app at a time. That's why there's the setting to tell VAB to only use it every n seconds (for a second at a time).

Thanks a lot. Will include it ASAP, but it will still take a while because I had to redesign fragments (still working on it). They were causing too many null pointer exceptions. Stupid Google implementation, can't ever tell when Activity is actually available to the Fragment :silly:
[Android Apps and Games] sampalmer:
Screenshots affected by superdimming

I've noticed that when I use my Sony Xperia M's "Take screenshot" function while Velis Auto Brightness is using super dimming, the screenshot is also dimmed. Is it possible to fix this so screenshots aren't affected by super dimming?
[Android Apps and Games] velis74:
Unfortunately no. There's no indication for VAB when a screenshot is being taken and there's no way for me to override system's screenshot functions. In fact, Google provides no API whatsoever for taking screenshot, believe me, I've researched the subject to great length.
[Android Apps and Games] donjoe0:
I thought I could tweak the lower-light levels by combining Superdimming and Additional Percent to Add, but Superdimming is refusing to work at 0 lux and 0% screen brightness (which is stupid, as that's exactly where I want it to give me a darker screen) and so is Additional Percent to Add (it adds nothing, no matter what values I enter). This is on an ASUS Padfone 2.