yashsingh1/xdaforums huggingface dataset:
[Android Apps and Games] velis74:
Sorry for the late reply, been a busy weekend...

This is the thing with devdb. The mobile app doesn't see devdb tabs. The apk is available in the downloads section when viewed from your PC browser.

No

What exactly do you mean here? You set it to 30 seconds, but it still reads as fast as possible?

No problem, will add this.

I will also try to get my hands on an SGS 3 mini to see if I can duplicate your issues.

Both Tasker and Locale display VAB icon next to its entries so it's easily distinguishable. I'll take a look at llama, see if I can make something work. (5 minutes passed) - I went to llama web site and there is no mention of plugins whatsoever. I will have to contact the developer to get some info on the matter.

Yes, but the problem is that profile buttons apply a profile which is not exactly a single value, but an entire graph. I would have to compare entire graphs if I wanted to display that + what do I do when you have a profile selected, but change the graph? I can't figure out a good solution for that either.

Also I have now promoted the last update to full version, available for all + there should be another update shortly with some nice (and very requested) fixes.
[Android Apps and Games] velis74:
3.55.161 (10.2.2014)

Added current brightness to main screen and notification\n

FIX: sidemenu now implemented in android-standard way (slide from left / right)\n

FIX: FC on Galaxy Note 10.1 (http://stackoverflow.com/questions/...d-color-file-when-launched-on-a-galaxy-tab)\n

FIX: a gazillion small things that once worked or never worked at all\n

Uploaded to OP, downloads and Play store
[Android Apps and Games] Pkt_Lnt:
I can not get into the menu. Slide left to right (or right to left) does not work, Menu button does not work. I have an S4 Active with no navbar, but physical menu / home / back buttons.
[Android Apps and Games] sunsero:
Yes, the camera reads on S3 mini seem much too often - when they've already started. The only exception is the unlock screen, here it takes a few seconds until the brightness adjusts to the environment for the first thime.

Thanks!!

I see - Llama does not display an icon beside the Locale actions. If you install Llame - well, it requires lots of permissions but NOT full internet access, so I consider it rather harmless - you can add actions that will be triggered on certain conditions. The easiest condition is to create a desktop shortcut from your launcher to a special rule having as action to call a Locale plugin which sets a certain VAB profile. Mostly on my Lenovo B6000 with light sensor the new graph applies with this immediately correct but on S3 mini with camera it seems most of the time to activate the profile chosen before instead (if you have different shortcuts to different light profiles and switch between them - experimented with three different profiles all containing super dimming).

Also the latest version still does not put the red cross onto the graph of the new profile immediately when the profile is selected via desktop shortcut on S3 Mini. The red cross is put immediately on the graph when you select a new profile from VABs main screen, however.

As a first step it would be good if the chosen profile was somehow marked as selected or highlighted. If the graph does not match any profile no profile can be highlighted of course just like it is now...
[Android Apps and Games] bornoxt:
Works fine on my N5.
[Android Apps and Games] velis74:
Slide from edge of screen.

I will try to make the menu button work tomorrow if I can.
[Android Apps and Games] Pkt_Lnt:
Ok, got it now. Part of the issue was my Otterbox case. I have to touch, hold briefly, then slide. Don't worry about the menu button unless you want. Some apps will only let me get in with it, but otherwise I use touch screen menu access.
[Android Apps and Games] velis74:
No, actually I was planning on including an action bar just for the menu icon so that things are a bit more obvious. As it is, it's not exactly clear that the app even has a menu.

BTW, what's that "SLO" as your city?
[Android Apps and Games] Pkt_Lnt:
Makes sense, thanks.

San Luis Obispo, coastal California halfway between SF and LA. My avatar is the namesake mountain in the middle of town. :good:
[Android Apps and Games] velis74:
Ha ha, stupid me. Here I thought for a moment you were from Slovenia :D Didn't make sense with US listed as your home country though :o
[Android Apps and Games] brian.williams:
galaxy note 2 brightness keeps jumping (still)

I have loaded this .161 version on the note 2, but I still see the light readings jumping around. Since I don't see anything specific in the change log, I guess this isn't the version I am waiting for to test.

I find starting velis much nicer with the menu starting off-screen - the graph used to jump around a few times before it would settle.
[Android Apps and Games] velis74:
Unfortunately I don't know anybody with a note 2. Is it possible for you to describe this light jumping in more detail? Does the sensor go up / down erratically, especially when there's low light?
[Android Apps and Games] velis74:
3.55.162 (11.2.2014)

Menu key now opens menu

App titlebar now displays that there's a menu to be opened (and opens it)

Floating point lux values: much greater precision for low sensor readings

Some battery usage optimizations

Camera now respects grab interval setting

New language: dutch, thanks to Maardiweb

Uploaded to OP, Play Store. Not to downloads though, the "add file" button doesn't seem to work right now.
[Android Apps and Games] sunsero:
Just took a quick glance at .162, the camera read interval seems to be respected now.

However I have a graph like this:

Pt: 0,0000 7

Pt: 1,0000 15

Pt: 62,0000 30

Pt: 1000,0000 255

Pt: 15000,0000 255

Now, when the camera reads a brightness of 0 the display becomes quite bright, e.g. jumps up from 6% to 15% though it should lower to 2% like it did with the previous version.
[Android Apps and Games] velis74:
3.55.163 (11.2.2014)

FIX: Lowest brightness point wasn't being used after optimisations

Sorry about that :(
[Android Apps and Games] sunsero:
Seems not to be on Play Store yet. Btw, any reason the apk size increased iirc recently from about 600 kb to 1,1 MB?
[Android Apps and Games] RovG:
[MENTION=2424510]velis74[/MENTION],

Thank you for the UI changes. It was certainly worth the wait.
[Android Apps and Games] sunsero:
With .163 lowest brightness works again, VAB keeps improving. :)

Regarding camera read interval - when the display was turned off, is the first read from the camera after turning on the display again immediately or does it wait the camera read interval? I'm asking because when turning off the screen in a low brightness environment and turning it on again in a bright environment it still takes quite a while before the display becomes brighter and thus visible enough to swipe the unlock pattern.
[Android Apps and Games] sunsero:
Regarding the non-matching red cross after changing the profile via a llama shortcut, I've attached now a picture. Actually the blue graph displayed is defined in none of my profiles, so this might also be related to the issue.

P.S.: The wrong graph seems also to be shown shortly without llama when pressing the back button in the main window before it disappears.
[Android Apps and Games] velis74:
I have no idea. Seems like the latest update to Android SDK copies all the languages to their sub-languages, e.g. en to en-gb, en-us, etc. Each language brings quite a bit of size and Developer console said there to be 55 new languages when I first uploaded last week.

I agree. That side menu really sucked though it wasn't without advantages to be able to always see it. Well, now the 4.5" devices and up will all show menu in landscape mode by default.

I just re-checked: the sampling takes place immediately. However, one round of sampling (one single pic) takes more than two seconds on my phone. Is the time to response even longer on your phone?

You should set the screen-on override to some value that at least provides a readable screen in a bright environment.

The blue line is your superdimming threshold, which is set too low to take effect BTW. For superdimming to take effect, the graph needs to go below the superdim threshold. However, yur description worries me: the blue bar should only be drawn if you actually have superdimming enabled. From what you are saying this might not be the case?

It seems like your brightness isn't adjusted because brightness calculations fail for some reason. Maybe there's no sensor reading at the time? Will check code paths again.
[Android Apps and Games] sunsero:
Will check for a while now if my phone takes more than 2 secs for the first read, I'm not so sure about this anymore now. But I also just changed from a very processor intensive live background on the desktop (not the lock screen) to a static one. Maybe this is related anyway.

Regarding superdimming: Yes, I've enabled it and I'll attach another picture showing the actual graph with working superdimming. But in the picture posted previously the graph (light blue one! ) is a graph that I never defined and the red cross also does not match the light blue graph.

The only sensor enabled in this scenario is the front camera, all other sensors are turned off in VAB's settings.
[Android Apps and Games] velis74:
VAB will use a safe preset which is "TFT normal" if after parsing there was no valid line or if the first point wasn't for lux == 0. Perhaps one of your presets is faulty in this respect?
[Android Apps and Games] velis74:
More of a follow-up post than anything:

[MENTION=5620101]xaverg[/MENTION] - your issues with note 10.1 should now be resolved
[MENTION=4403217]Pkt_Lnt[/MENTION], [MENTION=5615286]dclarkg[/MENTION] - you're quiet on the subject that .161 introduced floating point lux readings for graph ;)
[MENTION=4177034]RovG[/MENTION] - is the values display in the notification OK?
[Android Apps and Games] dclarkg:
Updated to .163 on the play store, and works like a charm, is now easier to play with the graph and adjust it. For me this app is way better, faster and lighter than Lux. Great work Velis!
[Android Apps and Games] Pkt_Lnt:
Yes, I noticed it right away, since I keep the notification active and use it to fine tune on the fly, now I do not have to do that as much.

Yes, it is very nice to have, thank you. I punched the Thanks button, I just try not to clutter threads unless something is important; we really appreciate your work and responsiveness to comments. I like the new avatar too, will that make it to the app icon? :good:
[Android Apps and Games] sunsero:
I don't think this could be the reason because the profiles work when activated manually using VAB's user interface. But with latest releases activating profiles via Llama's Locale interface emulation became very unreliable. With the older release there were issues on S3 mini, with the current version it also does mostly not work anymore on my B6000 tablet. So would be great if you could recheck with Llama or Tasker/Locale if the profile selection via the Locale Interface actually still works correctly for you.
[Android Apps and Games] brian.williams:
Yes, that is exactly the behaviour. It is only in buildings and trains etc, where the light reading is low, say below 200. I have noticed one room at one point I could hold the phone in one position and get one reading, and then just tilting it a couple of millimeters could make the value jump up/down. I suspect the tilting may means it is "seeing" more light from a window behind me, so perhaps it is quite sensitive to any polarization or angle of the incoming light. So even though I don't see a change in light level, the sensor may do so. I didn't see this problem earlier on the 4.2 rom with the standard brightness controls.

It also didn't seem to be applying the smooth transitions. I had set smoothing override to 99999 percent to try to stop it jumping under any condition, but it seems like 0 may work instead for that instead.

I have brightness sensor turned on, and under that is specific the lux sensor access method. If I select it, there are two options:

- capella microsystems, inc. v1 0.75ma

- a line which is blank, except for the radio button so I can select it
[Android Apps and Games] bornoxt:
Something similar happens to my phone after charging wireless over night.

If I switch the display on in the morning and open VAB it uses the "TFT normal" instead of a modified "AMOLED dark" I use usually.

After switching back to the modified preset it works fine until the next night.

And also if I leave VAB via the back or home softkey on my N5 I see for a fraction of a second the "TFT normal" line in the graph bevor the app disappears.
[Android Apps and Games] velis74:
I will install llama to see how it works on my phone.

Seems like Note 2 has the same sensor as SGS 3. Usually this is fixed by setting smoothing time downwards to a large value, like 15000ms.

I just got an idea how I might be able to fix this. Maybe I can cook up something soon.

Smoothing override of 0 means no override - it works just like 100 or any higher number as there's no override in such a case.

That second sensor option is a bug. I'll try to locate it.
[Android Apps and Games] velis74:
No, that's the company logo, I'm making a push for going solo. I will have the icons redesigned in the near future, as soon as I finish designing the next app. I think by now this app deserves some professionally designed icons :)
[Android Apps and Games] bornoxt:
It happened again. :(

After wireless charging over night, VAB switched back to “TFT normal“.

This behaviour started after the update with the hidden menu bar.

Is there any way I could help you to solve this problem [MENTION=2424510]velis74[/MENTION] ?
[Android Apps and Games] velis74:
What is your language? Does manually switching profiles exhibit the same problem?
[Android Apps and Games] bornoxt:
German

Manually switching the profiles works fine.

Only thing is that if I leave VAB via the back or home softkey on my N5 I see for a fraction of a second the "TFT normal" line in the graph bevor the app disappears.
[Android Apps and Games] velis74:
That is sort of intended: the UI uses safe preset when not connected to the service and when exiting the app, it will first disconnect.

Do you have option to record a logcat? (need root for that)
[Android Apps and Games] bornoxt:
My N5 is rooted but I don't know how to record a logcat.
[Android Apps and Games] Pkt_Lnt:
Tutorial how to logcat

http://xdaforums.com/showthread.php?t=1726238
[Android Apps and Games] velis74:
Pkt_Lnt posted link to a good guide. I too use catlog for device-based logging.

Log level must be at least 4. Set it through dev options dialog (long-press proximity reading on main screen).

Naturally, the log should be for the night when the profile will reset to TFT.
[Android Apps and Games] sunsero:
[MENTION=2424510]velis74[/MENTION]: Could you also add some basic error logging / displaying for non-root users? E.g. showing exception texts in a toast message might already be helpful.
[Android Apps and Games] velis74:
There aren't many exceptions in the app. Usually such problems stem from strange event combinations -> hence the need for logcat.

I could add log recording to the app, but so far this wasn't in a particulary high demand.
[Android Apps and Games] bornoxt:
I've installed catlog yesterday but unfortunately it didn't happen tonight.

Are there any other settings I have to change in catlog?

Or just start the app let it run in the background over night and save the log in morning and send it to you, maybe via pastebin?
[Android Apps and Games] D1Ltd:
With the last version (.163) i can't manually edit the graph values.

No matter how i always get a error message saying some of the points are incorrect and then it reverts back to the preset profile; this happens even if i don't change any value and press accept.

Enviado desde mi LG-D802 mediante Tapatalk
[Android Apps and Games] bornoxt:
Same here! :(

I have some manual edited presets I set up with a previous version of VAB and they seem to work fine with the actual version.

But if I try to change values now and hit OK I get the same error like [MENTION=4521625]D1Ltd[/MENTION] .
[Android Apps and Games] sunsero:
Same here as well...

---------- Post added at 12:27 PM ---------- Previous post was at 12:03 PM ----------

If I change the graph from e.g.

Pt: 0,0000 3

Pt: 20,0000 30

Pt: 100,0000 100

Pt: 15000,0000 255

to

Pt: 0.0000 3

Pt: 20.0000 30

Pt: 100.0000 100

Pt: 15000.0000 255

then I can save the changes.

So the decimal point must be the issue:

VAB outputs a localised decimal point but accepts only the English notation of it.
[Android Apps and Games] D1Ltd:
[/COLOR]If I change the graph from e.g.

Pt: 0,0000 3

Pt: 20,0000 30

Pt: 100,0000 100

Pt: 15000,0000 255

to

Pt: 0.0000 3

Pt: 20.0000 30

Pt: 100.0000 100

Pt: 15000.0000 255

then I can save the changes.

So the decimal point must be the issue:

VAB outputs a localised decimal point but accepts only the English notation of it.

Yep, just tried this and it works.

Thanks!

Enviado desde mi LG-D802 mediante Tapatalk
[Android Apps and Games] bornoxt:
Am I right that the decimal values are only available since one of the latest updates?

In the .153 version there were only integers, I think.
[Android Apps and Games] sunsero:
Yes, the increased precision was introduced just recently.
[Android Apps and Games] velis74:
Actually, the log is a circular buffer in the OS itself. It doesn't really matter when you start the app, it will read the entire log that is at the time available. Normally, that is long enough for me to see events in the past few hours that would reveal why the graph was reset.

Fix for decimals coming up shortly (shame on me, I'm from comma delimiter country myself and didn't notice this glitch). Also a possible fix for Note 2 / SGS 3 sensor.
[Android Apps and Games] bornoxt:
Ok, next time this happens I'll send you the log.

I noticed also that VAB starts with the "TFT normal" graph after a reboot of my N5.

In version .153 it started with the last used graph.

Is this maybe a result of the decimal problem?
[Android Apps and Games] sunsero:
[MENTION=2424510]velis74[/MENTION]: A while ago you asked for ideas regarding Tasker/Locale actions: It would be nice to have actions for next and previous profile so you could rotate through them using shortcuts for Llama (when it works). My idea would be to define shortcuts for Llama in the Frontmost app which provides user-definable semi-transparent on-screen buttons that could then switch to next or previous VAB profile.
[Android Apps and Games] velis74:
I believe this is the same problem that activates TFT normal on your phone. Maybe it is linked to the decimal problem. We will see soon, I'm doing final tests of the app and will release in the next hour, hopefully.

Currently I do not track profiles as you know. I have added a TODO to track profiles, then even such scenario will be possible.
[Android Apps and Games] bornoxt:
[MENTION=2424510]velis74[/MENTION] Sounds good!

And no hurry, I can wait as long as the app works in general.
[Android Apps and Games] velis74:
3.60.164 (15.2.2014)

Added option to try and reduce erratic sensor readings in some devices (most notably SGS 3 and Note 2)

Turning off interactive notification for Android 4.3 and up is now a regular settings option

FIX: manual graph edit didn't work for many locales

[MENTION=4109502]WibblyW[/MENTION]: The erratic readings fix might help your hunting issues as well.

Uploaded to OP and beta. Downloads again doesn't work :(
[Android Apps and Games] sunsero:
Can't find it in OP :-/
[Android Apps and Games] velis74:
Now it should be there. Seems previously it didn't upload correctly.
[Android Apps and Games] sunsero:
I wonder why can't VAB not simply remember the name or index of the selected profile?

---------- Post added at 11:56 PM ---------- Previous post was at 11:45 PM ----------

According to a quick test this seems to have fixed switching profiles using Llama with Locale/Tasker option as well. Checked both on S3 mini with front camera and on B6000 with light sensor. :thumbup:
[Android Apps and Games] velis74:
That's exactly what it will do when implemented.

This is so impossible. Are you sure llama wasn't updated as well?
[Android Apps and Games] sunsero:
Well, Llama was updated yesterday morning but I had checked VAB after that as well and it did not fix the issue. Isn't it possible this was also related to the commas? Anyway it definitely started working right after VAB's update.
[Android Apps and Games] velis74:
I'm glad it's working for you now, but I doubt yesterday's fixes had anything to do with it as your problem began before version with floating point lux readings. I was just about to install llama to see how it works on my phone...
[Android Apps and Games] sunsero:
There still seem to be some issues as on the tablet now it seems again the wrong brightness gets applied via Llama shortcut. It worked yesterday with the new version o.g. VAB but now if I choose the bright profile the display becomes dark and vice versa. However, i think it's not the wrong profile activated but rather the red cross does not move right onto the light blue curve. Instead the red cross moves to where the curve of the previous via Llama activated profile had been.

So yesterday's VAB update generally made switching profiles via Llama shortcuts possible again but the old issue of the sometimes wrong brightness after that does not seem to have fixed by yesterday's update.
[Android Apps and Games] Pkt_Lnt:
Just as an FYI, I use Tasker to switch brightness profiles based on numerous events, i.e. connect or disconnect home wifi, calendar event work start, location at bus stop, movement in vehicle or on bicycle. Everything changes as designed with no errors, and it has worked for me for many months.

I do this on my SG4 Active and Nexus 7.2013 many times a day. Both have normal, bright, custom, and curve profiles defined.
[Android Apps and Games] sunsero:
With Llama I do shortcut pressing triggered events, at least they don't apply immediately like they should. I also have an navigation app running based rule and I think this works, but it might take a while until the brighter brightness level gets applied. So maybe the point is that it needs some time until the brightness adjusts to the curve of the new profile.

P.S.: Update - I checked on the tablet (with the light sensor) again and it actually seems the red cross syncs with the light blue curve of the new VAB profile that had been chosen via Llama shortcut as soon as the environment brightness changes.

P.P.S.: I also checked on the S3 mini (with front camera as only sensor) and at least in this test the brightness level adjusted immediately after choosing a new profile via Llama shortcut. However I'm not sure if there's some other condition required to trigger an erratic behavior, but of course I would write again if this happens.
[Android Apps and Games] Pkt_Lnt:
All my Tasker changes are automatic, I have no shortcuts of any kind in the launcher.

Another Llama user in the TimePIN thread has been having issues with Llama not switching unless the screen is on. I wonder if that is affecting you in some way, however if you are pressing a shortcut, then obviously screen on is not a factor. Supposedly Llama and Tasker use the same Google API, but maybe this needs to get to the attention of the Llama dev, and it is not just an issue with VAB?

Good luck.
[Android Apps and Games] sunsero:
Hmm... any idea why the new curve is shown but the red cross does not sync to the curve before the environment brightness changes? Is it possible for you to create shortcuts on the launcher for Tasker actions? Then we maybe could find out more if it's a Llama issue which I don't expect it to be but you never know of course.

Regarding the screen on requirements I think some devices do not update the cell id when the screen is off therefore iirc Llama has an option to periodically turn on the screen to read cell ids...