yashsingh1/xdaforums huggingface dataset:
[Android Apps and Games] Pkt_Lnt:
The red bars track the blue curve always for me. If I understand you, I have attached a short video that shows it.

https://www.dropbox.com/s/a85vxc7uj7j9q9s/VID_20140217_185220.mp4

Tasker still has a steep learning curve for me, and I learned how to do what I want automatically. It is possible to create shortcuts in the launcher, but I ran out of time trying to figure it out, I'll try again in a couple days.

The TimePIN I mentioned is a lockscreen PIN security app; allows Tasker/Llama to activate of deactivate say if you are connected to a known wifi. That is the one the guy with Llama is having issues, because it comes up locked even though he is connected to his home wifi, so he has to unlock the screen since Llama will not switch while the screen is off. My setup with Tasker has TimePin disabled and slide enabled when I walk into the house.
[Android Apps and Games] sunsero:
That's quite what it looks like here normally. But after changing profiles with a Llama shortcut I open VAB via the button in the notification area and I see that the curve changed but the red cross does not move onto the curve until the environment brightness changes. Btw: The light sensor of the tablet has no fine resolution, e.g. with the tablet being the only light source in the room it says 20 lux, and it requires much more light to go to the next available step which is displayed by VAB as 90 lux.

Thank you, I'm curious for the results!

AFAIK not every firmware allows for disabling the Pin without the display being unlocked. It makes sense from a security aspect of course to require the user to unlock the display once manually before the pin gets disabled.
[Android Apps and Games] sunsero:
[MENTION=2424510]velis74[/MENTION]:

Is it possible to change VAB in a way that it does not require a change in environment brightness to apply to the display the brightness of a new profile curve that had been chosen via Tasker/Locale immediately?
[Android Apps and Games] velis74:
Sorry for the time, we've got winter holidays here and kids are all over me :)

VAB already should activate the brightness according to the newly selected curve. I'm trying to find the reason why your particular devices wouldn't do it, but they definitely should.

Edit: I was able to reproduce this by creating wrong llama shortcut icons. When I had one for a profile and one for an event, even my widget didn't work correctly. then I "fixed" it by creating two event shortcuts. Then everything started working. Now to try and duplicate it again :)

Edit 2: Darn this!!! the fun lasted a short enough time. I can't reproduce it any more :(

Edit 3: Even after creating two more VMs, I cannot reproduce the problem. Maybe I need to wait it out a little :p

Edit 4: (Seems I'm feeling talkative tonight ;) ) I managed to reproduce the issue and have fixed it. Finally!!!

Expect release shortly.
[Android Apps and Games] sunsero:
That's the point, the issue is sometimes hardly reproducable. I almost thought you might never be able to reproduce it or even track it down. So I'm very glad that you could reproduce it now and hopefully also could fix the issue.

Looking forward to the release! :)
[Android Apps and Games] velis74:
Ran out of time yesterday. This wasn't the only change I did so I have to pack some things together before I can publish.
[Android Apps and Games] velis74:
3.60.166 (24.2.2014)

Collapsible settings groups for easier navigation

Excluded apps memory and performance improvements

FIX: when sensor returned 0, some app functions didn't work correctly

FIX: Sometimes changing profiles didn't work correctly

Currently only in OP and beta. The changes to settings screen are too extensive (internally) and I'm not brave enough to just publish it to general public :)

I'm curious what you guys think of the collapsible settings groups. Is the general idea in the right direction?

Edit: Also, would anyone be interested in multiple app themes?
[Android Apps and Games] sunsero:
Thanks, did a quick test and Llama shortcuts worked on the tablet :thumbup::thumbup::thumbup:

Regarding the collapsing in the settings menu - I think I like it and it's a good direction to go. What I'd like here in addition would be on the top two buttons to expand or collapse all groups. However, I guess this is something that's already on the roadmap, isn't it? ;)

---------- Post added at 09:54 PM ---------- Previous post was at 09:40 PM ----------

Tried FrontMost app with a button that sets via Llama shortcut on Fling Up action a bright profile and on Fling Down action a dark profile. Very nice as it allows you to change the brightness profile in any app without having to go to the homescreen or use the notification area.

Well, there also seems to be some issue with this: there's some strange flickering when changing profiles like this and the app is e.g. Gmail or Xda Developers. There's no flickering when flinging up or down the FrontMost button when Nova Launcher is the active application.

Edit: On S3 mini the lux value shown in the app and in the notification area currently differ, e.g. app shows 4 lux, notification area shows 0 lux.
[Android Apps and Games] sunsero:
Lux values differ on the tablet as well, e.g. 55 lux in the notification area and 90 lux in the application. (the light sensor in the tablet supports actually in this range only reading 20 and 90 lux, so 55 seems a virtual value on the way up from 20 to 90 for smoothing)
[Android Apps and Games] velis74:
This is normal: Updating notification is HUUUGELY batery-intensive operation. Since notification progressbar isn't all that precise anyway in displaying the current brightness, I only update it when there's actually someting to update. The displayed figures likewise take a hit as they are updated at those same times.

If you find that really annoying, I could attempt to fix it with a mandatory update every 5 secs or so. Anything below that would significantly impact the battery I think.
[Android Apps and Games] kantjer:
testing now report back in 10 minutes.

EDIT Screen on - Screen off sensitivity threshold, set to 4%
[Android Apps and Games] loneagl:
Hey great app.his rate it 5 stars
[Android Apps and Games] :
Well yes please, the ability to set each step to make it easier so I could set both 90 & 160 to say 10% to stop the jittering I'm getting at the moment.

Tried Lux also and this is far better as Lux simply doesn't work well at all on my phone. Does anyone else have the HTC One S that is testing this to see if its just my sensor or is how everyones behave on the phone?
[Android Apps and Games] velis74:
Today i have been able to reproduce the no reading issue, but unfortunately the log wasn't verbose enough.

Now logging the hell out of it and hoping it happens again soon.

I may also have something on those brief flashes, but again, the logging was weak and i need dayliht to replicate the issue.

I hope to have something on these soon.
[Android Apps and Games] bgx:
Hey velis!

Youre app is great but when it is active the baseload is grown up! Means when I not touch the phone and look in setcpu I get a baseload of 400-500 mhz. When I freeze your app my baseload is back to the min of 200mhz.

This is a no go for me and I think I will stick with my tasker and cm10 based automated backlight...

sorry! :(:p
[Android Apps and Games] kantjer:
Just checked my phone and I'm seeing the same. The minimum cpu speed is 400 mhz, and with the app frozen the minimum cpu drops to 100 mhz.

That would explain the higher battery use.
[Android Apps and Games] THE RED BLUR:
Yes I'm afraid that why I stopped using it. Maybe with some more time it will be sorted;)

PHONE : SGSII

Sent via: Tapatalk 2

Main ROM: RR ics 2.7

2nd Rom RR JB 3.0.9 BETA B4 (ONLINE )

KERNEL : Dorimanx 5.83 B6

MODEM : LPS

ROOT APP : SuperSu
[Android Apps and Games] velis74:
Thanks for this. I think it confirms my suspicions. I'm adding some code to periodically check for screen off which should significantly drop usage during screen off. I'm still diagnosing why the app should work so hard when screen is on as well. I'm suspecting the sensor may be yielding values like 4, 6, 4, 6, 4, 6 in rapid succession which my threshold code can't eliminate.

Yes, this is the consequence of the app working on something it shouldn't work on. The kernel sees CPU usage and raises frequency as the result. bgx, I am trying to determine the cause of this usage and make the app work for you as well, even if you are sorry ;)
[Android Apps and Games] velis74:
I think i found the cause for battery consumption. Tomorrow i upload the fix, just need to test it a bit before that.
[Android Apps and Games] kroz:
looking forward for that, ;)
[Android Apps and Games] grzesiek1945:
Good news, because imo battery consumption is the biggest problem of this app :/

Wysyłane z mojego GT-I9100 za pomocą Tapatalk 2
[Android Apps and Games] velis74:
1.10.31 uploaded

Contains battery fixes only. Hope I didn't mess everything up :)

Sensitivity threshold is extremely important for this when screen is on, so set it to at least 2%.

Added a ton of other detections and fixes. While screen is off, the app SHOULD NOT consume battery any more.

Cooltool says for my phone that my app isn't significantly different to system auto brightness any more in regard to battery consumption.

Edit: Just completed 30 minute runs with screen on and off. In both cases velis auto brightness didn't even register in gsam battery monitor. I wonder if it even works any more? }: ))))
[Android Apps and Games] kantjer:
Thanks, I wil try it out as soon as Play Store is updated. :good:

I will report back.
[Android Apps and Games] lou2s:
Thanks, hv been reloading play store and the update is not there yet. So eager for the update.
[Android Apps and Games] xanthrax:
Some bad news after the new update

AOKP rom, AOKP kernel

check pics

Brightness sensor get crazy

⇄⇄⇄⇄⇄

To be more precisely, I noticed that cool tools shows me all the time the maximum level for CPU frequency. I thought it's a cooltools app bug but this happened after the installation of the new velis update.

playing around it I noticed the difference ... please confirm or not
[Android Apps and Games] kantjer:
Just installed the latest update 2 minutes ago, and my cpu speed is falling back to 100mhz again (using the ROM control - performance screen)

Will do the battery consumption test next.
[Android Apps and Games] :
Installed latest and seems to be running very well so far. The transitions are alot smoother now, still look a little jittery but that's just being pedantic now (take that back as I've found the settings! Who would have thought? Hahaha) :D Thanks for your continued hard work sorting issues out it very much appreciated.
[Android Apps and Games] kantjer:
Here is the result of my 30 min test with screen off. VAB is still using a lot of juice.

sensitivity at 4%
[Android Apps and Games] lou2s:
One suggestion, can we set the screen brightness to the lowest at unlocking of the screen? Bcoz I hv set the service only react at a change of light >7%.

Thanks!
[Android Apps and Games] qqqqqq0:
which setting ideal
[Android Apps and Games] sunsero:
Isn't it possible to update the notification value when there's actually a difference between the value shown in the notification area and the value actually read from the camera or sensor? And if there's no difference don't update.
[Android Apps and Games] velis74:
Yes it is possible, but it takes lots of battery. These light events are extremely frequent on devices with sensors.

I'll see if I can do something about it, but currently I don't see how anything but a mandatory update on fixed interval would work.
[Android Apps and Games] sunsero:
Even if the updates are extremely frequent, isn't it possible to do something like this:

static int oldLux;

public void LightSensor_Update(int newLux) {

if (newLux!=oldLux) {

updateDisplayBrightness();

updateNotification();

oldLux=newLux;

}

}

Or is newLux changing on every event?
[Android Apps and Games] velis74:
Who gave you source of my app? :cool:

Joking aside, this is pretty much exactly how the sensor changed routine is programmed.

Yes, sensor changes are extremely frequent. As you know, sensor reading is a float value and floats have a pretty big range. Of course, actual hardware resolution is lesser, but still plenty enough to feed hundreds of these events per second if need be. Normally though, these events are not that frequent. Depending on sensor, a stationary phone doesn't generate this many events, but holding device in hands is usually enough to generate a few events per second.
[Android Apps and Games] sunsero:
Well I think if the value in the notification area is not up top date, it does not make any sense at all. Maybe only update it if the notification text actually would change since the last update and the last update is already a few seconds away.
[Android Apps and Games] velis74:
The value IS up to date, it's just 1/16 its normal precision. That said, I'll fix it tomorrow.
[Android Apps and Games] sunsero:
Hmm...55 does not look like 1/16 precision when the actual value is 90?
[Android Apps and Games] velis74:
It's a logaritmic scale for lux values.
[Android Apps and Games] velis74:
4.00.168 (6.3.2014)

When screen is touched, brightness is not updated for specified time (a new setting - also in wizard)

The above setting isn't active when VAB is frontmost app

Notification is updated at least every 5 seconds (is now more precise)

Unconditional additional brightness

Additional brightness accepts negative numbers (will decrease brightness)

FIX: Wizard back button now actually works + wizard page count fix

FIX: After wizard, settings screen is refreshed to show selected values properly

Posted to OP and Play store beta.

This release is very important for me from stability viewpoint. I made lots of code optimizations / rearranging and I'd very much like to hear if things remain stable.

I'd really like to hear some feedback on the steady screen feature (the screen touch setting in sensors section). It was pretty hard to figure out how I can detect user activity and I've been wanting to add this feature for more than half a year.

Typically you'd set this to a large value, say, 30 seconds, so that the screen doesn't flicker while you're using the device. Seems pretty handy on my Nexus 10, screen now stays solid while I browse / type / play games.

Off to updating the manual now.

Edit: manual updated.
[Android Apps and Games] sunsero:
Hmm...seems brightness is no more applied to the status bar/notification area. At least the display is no more superdimmed there, only the rest of the screen.

---------- Post added at 09:58 PM ---------- Previous post was at 09:08 PM ----------

Other apps doing an screen overlay like FrontMost and its Quick Controls also at least under some conditions like after unlocking the screen no more respect the superdimming. Really hope you can make this work again soon.
[Android Apps and Games] velis74:
I was afraid of that, thanks. I had to decrease level of overlay in order to be able to detect the touches. Will fix.
[Android Apps and Games] bornoxt:
Works on the whole screen on my N5.

The new screen touch feature is nice.
[Android Apps and Games] velis74:
A fixed APK is uploaded to beta play store and OP. [MENTION=5221171]sunsero[/MENTION]: can you please check how it's working now?
[Android Apps and Games] sunsero:
Quick Test: Works again on tablet and phone now. Also lux right in notification area.
[Android Apps and Games] lklaus:
Hi Velis,

I'm still on the one before, so may be it's obsolete by now, but on my s3mini with Maclaw's CM11 Rom VAB does not anly longer handle brightness on the lock screen? The3.x version did this

Klaus
[Android Apps and Games] velis74:
Is that on .168 or .169 version?
[Android Apps and Games] lklaus:
I'm still on .168

Klaus
[Android Apps and Games] velis74:
.169 should fix that.
[Android Apps and Games] velis74:
I have just published a new release to PlayStore beta.

There are no functional differences, I just massively rearranged code and moved all non-VAB related code to a library.

Everything should work as before, but please let me know if your purchased content stopped being available or something.
[Android Apps and Games] kantjer:
Everything seems to be working fine.
[Android Apps and Games] sweetpiggy:
very usefull app :)

suggestions (if i can :))

1 notification can looks way better.... uniforming his graphic to android design ;)

2 maybe notification nees a high priority (then that no more jump on first/last/second/.... position on notification tray ;)

thanks for your work :)
[Android Apps and Games] bornoxt:
Didn't happen on my phone, stays always at the lowest position and I like it that way.

[MENTION=2424510]velis74[/MENTION] Latest version (.171) runs fine. Great work!
[Android Apps and Games] sweetpiggy:
really....! sorry, my mistake! ;)
[Android Apps and Games] bornoxt:
No need to apologize. ;)

Did you use any app to modify the priorities of the notifications on your phone?
[Android Apps and Games] sweetpiggy:
no, i don't. :)
[Android Apps and Games] ralpheboyo:
....so sweeeeeet first time ever I get 7+ sot hrs on the phone....loving it....best of all the transition affects are so smooth....

....just discovered this app....wow...excellent....got to get my head around all the settings...the manual is very helpful...once again excellent app...

Tapatalk: Nexus 5 (Art): SlimKat: ElementalX

---------- Post added at 12:46 PM ---------- Previous post was at 12:31 PM ----------

Tapatalk: Nexus 5 (Art): SlimKat: ElementalX
[Android Apps and Games] Gynoid:
Systematic crashes on my Huawei G740 (JB 4.1.2, rooted). Anything I could do to investigate?

Sent from Tapatalk
[Android Apps and Games] velis74:
Can you elaborate? What are you doing when it crashes?
[Android Apps and Games] Gynoid:
Two possibiliies:

1. Just starting the application, directly after downloading it from the Play store;

2. From the app settings, pressing the 'App store' button.

Either ways, I sent crash reports

Sent from Tapatalk 4.4
[Android Apps and Games] velis74:
I can only see one crash report for android version 4.4 (nexus 5). Are you sure you completed the send crash report procedure?
[Android Apps and Games] Gynoid:
Yessir, definitely. But I will reinstall the app and re-send the crash reports in the next 2 minutes.

:)

EDIT: Done ! You should have received 2 crash reports, now - one for each crash condition. Please note, this is based on the beta version.

---------- Post added at 10:22 AM ---------- Previous post was at 09:59 AM ----------

Got them now? Just FYI, my (beta) version number is 4.00.171
[Android Apps and Games] velis74:
No, still nothing. Maybe it takes a while for developer console to register these reports. I'l wait a couple of hours to see if that's the case.
[Android Apps and Games] Gynoid:
Is there any alternative/additional reporting tool I should use? I've removed Gmail from my (rooted of course) phone and am using another email client instead. Should I reinstall Gmail (if necessary for crash reporting) (: ?
[Android Apps and Games] velis74:
I don't know. I didn't think it took gmail to report a crash. When an app crashes, you can choose to either close it or send report. If you decide to send a report, you will be redirected to a page where you will have to accept the Google terms for that and also choose whether to send additional info about the crash. I don't know what the actual mechanism for sending out the crash report is. I didn't think it was by mail, but it may as well be.
[Android Apps and Games] Gynoid:
Okay, give me 5 minutes, and I'll sort this out. There has to be something I should install. Please stay tuned.

---------- Post added at 11:07 AM ---------- Previous post was at 10:36 AM ----------

Ok, seems like it should be an automated process, but it doesn't seem to work with me - I now have a number of bugreport.txt files stored on my phone. And if they're still here, it's probably that they haven't been sent yet. Just to avoid spending the night on this, do you have an email address I could manually forward them to?
[Android Apps and Games] velis74:
Sorry, didn't get notified about the edit: just send them to jure.erznoznik@gmail.com
[Android Apps and Games] trent25:
Bug report

First of, really enjoying Velis.

On a Nexus 5 (stock) I cannot seem to get "permanent additional brightness" to work. I tried the 3 different modes, non worked.

I want to cut the brightness down (negative percent), even at an extreme -50% I see no difference.

Using the latest version of Velis (4.00.169) from the Google Play store.
[Android Apps and Games] velis74:
I have rechecked the functionality, but I can find nothing wrong. Just in case I uploaded a recompiled .apk to OP / downloads section so that you may test on the exact same version as I. If it still doesn't work for you, I'd appreciate a logcat @ level 8.
[Android Apps and Games] sunsero:
With version .174 from OP there's a force close when clicking 'edit graph manually'. Hmm... seems quite unstable even for a beta - it crashes with other buttons like 'changelog' as well.
[Android Apps and Games] velis74:
Fixed, a direct result of me moving loads of code to a library. :p
[Android Apps and Games] velis74:
4.00.175 (7.4.2014)

FIX: Notification didn't properly update confirm / cancel button when they were pressed

FIX: There were some crashes reported through play store. This fixes them

Uploaded to OP and Beta Play store for now. If there are no bugs reported, it will also be moved to production in a couple of days.
[Android Apps and Games] pugsang:
[MENTION=2424510]velis74[/MENTION]

Just finished Greek translation of your app

File attached. Contact me if you need anything.

Regards
[Android Apps and Games] velis74:
Thanks. It might take a few days before I'm able to publish this though. I have just totally messed up the code because I want to introduce some additional functionality.

LP,

Jure
[Android Apps and Games] pugsang:
If you need any further translation of new features let me know by pm

Regards
[Android Apps and Games] Marx2:
This soft shows high cpu usage in stats. Does anybody see similar behaviour?
[Android Apps and Games] bieniu79:
Proximity sensor - idea for improvement

Hello. I use Samsung Galaxy S4 mini with S-View cover and I am looking for good customizable auto brightness app, because the built-in auto brightness control sometimes work in unexpected way under some circumstances so I wanted to have more control over it. I found Velis Auto Brightness very close to my ideal. The only problem I still have is related to using my cover. When it is closed it fully covers both light and proximity sensors. Now I have two options. Either I enable proximity sensor readings in VAB or not. With enabled I have a problem that when I open a cover and screen turns on automatically, I need to wait 3 seconds until VAB adjusts brightness. With disabled I have my display almost completely dimmed even in direct sunlight with closed cover (cover makes it possible to view a part of the screen, time and notifications are displayed there, so the screen should be readable even with cover closed).

I thought about possible solutions for this problem. I think that the simplest one would be to change how proximity sensor reading are used by VAB. Instead of disabling any brightness change for 3 seconds after detecting something covering the sensor, it could do such a restrictions only in case when light sensor readings would result in dimming the screen. If the light sensor shows that the brightness should be increased, it clearly shows that the brightness should be adjusted immediately, because even if the light sensor is partially covered by something, uncovering it will result in further adjusting the brightness up. In my situation it would solve the problem. It would work like this:

- When I close the cover proximity sensor reading prevents dimming the screen.

- When I open the cover and the light sensor shows that the screen is too dim, the brightness is adjusted instantly despite of proximity sensor readings.

Would it be possible to implement this kind of behaviour in VAB?