yashsingh1/xdaforums huggingface dataset:
[Android Apps and Games] velis74:
I will see what can be done.

Nice to hear that :good:
[Android Apps and Games] cukierkas:
Great app indeed. Thanks for update.

one more suggestion if u allow me.

Landscape support. When I'm writing SMS in landscape, sensor is covered, and lower brightness is applied. Can this be avoided in landscape? For example, when sensor is covered, the last brightness level is applied. That is implemented in CUSTOM AUTOBRIGHTNESS app. Can you add this feature?

Thanks in advance.

Sent from my GT-I9003
[Android Apps and Games] velis74:
This is what proximity sensor does.
[Android Apps and Games] cukierkas:
Sadly, but no, or not on my system at all :(

Just enabled proximity sensor, screen dims too much :(

When back to portrait mode, brightness level is left at same low level till I manually turn off the screen. After turning it on, app works grant. Amoled dim preset is applied, latest version, cache cleared......

Sent from my GT-I9003
[Android Apps and Games] velis74:
just verified myself. Seems my "fix" for proximity sensor wasn't a fix at all. Darn insects :D
[Android Apps and Games] cukierkas:
Take a deep breath, sometimes **** happens :)

Great app thought. :thumbup:

Sent from my GT-I9003
[Android Apps and Games] Redneck Trash:
It's working on my Galaxy Nexus.

Set from my toroplus
[Android Apps and Games] velis74:
I have added code to force text color for the buttons. You should not have any more problems with that. Coming with the next patch.
[Android Apps and Games] cukierkas:
hello again.

about proximaty sensors. if VAB uses them - can your app use proximity sensor and gyroscope to lock the screen as this app does?
[Android Apps and Games] supergaijin:
if it's not too difficult, would you be able to return to stock and test to narrow down whether the issue is with your phone's version of CM7 or the phone's hardware itself?
[Android Apps and Games] jackattack:
Why would an auto brightness app lock the screen? Why not just use the app you referenced?
[Android Apps and Games] cukierkas:
that would be nice indeed. all in one. why bother with two apps, when it can be implemented in one.

velis once said, that turning off screen with VAB is possible :)
[Android Apps and Games] Computoncio:
Why implement something that all roms has for default?

Let velis continue to develop what his got in the ToDo list.
[Android Apps and Games] CHEF-KOCH:
+1 :laugh: :good:

@ velis74

Hey, good news for you sir.

I just wanted to say that I have translated the tutorial into German. But i need to fix some lines so that other users understand it better. Maybe I can send your that file file or the source next week.
[Android Apps and Games] polobunny:
Some of the strings translated to French are a bit quirky and lose their meaning in the translation. Who should I get in contact with to correct/discuss this?
[Android Apps and Games] CoolApps:
This app actually works!

I wonder why Sony failed at the auto brightness software? :rolleyes:
[Android Apps and Games] CHEF-KOCH:
Hey, you can download all translations here.

If you have any problems, we can talk here about it here. Make a suggestion what string you would like to change. ;)
[Android Apps and Games] AbhishekS:
I've downloaded this app and it seems very difficult to set it up. What settings shall I keep to use the best out of this app?

What are the initial settings to get good amount of brightness in auto mode and also keep the battery life good?
[Android Apps and Games] velis74:
Did you read the manual?

As for settings, it's a matter of personal preference. I'm using defaults + amoled preset.
[Android Apps and Games] AbhishekS:
Where is the manual? I saw the first post of the thread and cannot find it there?

And what preset do you suggest amoled preset for Galaxy Nexus too or something else?
[Android Apps and Games] velis74:
App homepage links to the manual. Sorry i can't post link right now, i'm on phone.
[Android Apps and Games] kantjer:
But I can ;)

The manual can be found here
[Android Apps and Games] AbhishekS:
Oh thanks! And which preset do you suggest for the Galaxy Nexus?
[Android Apps and Games] peret2000:
Maximum brightness

It is a wonderful tool, and I also wonder why original rom does not work with the same precision.

The only 'but' I could say is: in hight light conditions (outside, a sunny day), maximum brightness is clearly not enough.

And I canno increase it (or I do not know how). With the original controller, I can set higher brightness.

Using HTC wildfire S with CM7
[Android Apps and Games] Pkt_Lnt:
Amoled, amoled dim, amoled bright, take you pick, try them all, see what I best or you.

-sent via Kindroid Jelly Fire Bean JB 4.1.1
[Android Apps and Games] velis74:
I don't know. The android brightness interface is pretty straight-forward: 1.0 means highest brightness and if you set the graph right, vab will set brightness to 1.0.

Did you try other apps and they don't have the same problem?
[Android Apps and Games] XT69:
default amoled is just perfect for almost every condition, amoled dim is also great for night :)
[Android Apps and Games] rcfcyl:
From what I can tell from my testing, the light sensor on the Galaxy Nexus kinda sucks. It reads 4/10 in a pitch black room with no lights on and 4/10 in my living room with 4 100watt light bulbs pointed pretty much right at the screen. I was hoping this app would allow me to have the screen at almost zero brightness at night to avoid glare and then raise the brightness so I could read it in my livingroom. Unfortunately it doesn't seem to work that way because of the ****ty light sensor in my phone. Running CM10 if that makes any difference ...
[Android Apps and Games] CoolApps:
Problem, even after testing the auto brightness, i switched off the auto brightness and then it really messes up the brightness, i could not change the brightness manually like when i try to change the brightness it just switchs lower until i uninstalled the application, i know i could of force closed the application via settings but i don't want to get such issue again :/
[Android Apps and Games] velis74:
I'm running ParanoidAndroid and experiencing no such issues. You must have faulty sensor if it only ever reports such low lux values. I'm getting 20-30 from monitor and up to 70 from living room lights. Enough for testing :)

Otherwise I am planning on using cameras to fix the bad readings in low light conditions. Should "fix" the minimum 4lux reading issue.

But later. Right now I'm finishing in-app store so that I can finally release Tasker / Locale functionality. Won't be long now: store almost running.
[Android Apps and Games] polobunny:
It's important to note that if you have a screen protector it can stop the light from getting to the sensor properly. I used to have a plastic one that made mine stay to 4 at almost any situation. I believe the way it was made it reflected light at a different angle and that messed up everything.

I also had one issue in my phone that my sensor wouldn't work, it would only show - 1. The fix was easy, fix permissions in recovery. :)
[Android Apps and Games] peret2000:
I have moved the graph to force maximun brightness with 1023 lux (that seems to be the max it can detect), but the brightness is not enough.

If instead I use the original settings of the rom (display setup), then I can get a brigthter screen.
[Android Apps and Games] sonwon:
Is this when you are only running on battery? On my phone an HTC EVO 4G when plugged in, the lowest light level it show is between 40-160. I haven't found a solution to this problem.
[Android Apps and Games] jackattack:
Is there a trick to setting the graph without causing peaks and dips? I can't seem to make a smooth curve unless I only do slight modifications.
[Android Apps and Games] Christiancs1969:
Batt:Dno probes so far all good;)

s2 aopk 412 dori 73 pitch perfect
[Android Apps and Games] supergaijin:
you'll probably have to wait for the manual editing like me. it's on the TODO list.
[Android Apps and Games] velis74:
2.00.59 (26.10.2012)

Tasker / locale support

In-app billing

Updated translations: slovene, german, spanish

However:

I'm not brave enough to just go and post this to market.

I need a brave soul or two to install the apk in the first post and try out how in-app store is working. Of course, you need to want Tasker support and be willing to pay 1€ for it in order to test this. Even if I messed up, you should not lose the purchase (the support will be enabled when I fix the reported bug) + you'll get a refund if asked.

The profile selection setting is enabled even if Tasker integration is not purchased so it should work in all cases. This will remain so for all eternity. :p The other settings / conditions should yield a message about purchasing tasker support and work if it has been bought.

*Holding breath...* :)
[Android Apps and Games] Pkt_Lnt:
You can breath at least once. ;)

edit - more breaths now that Google Play receipt has arrived. :good:

Galaxy Nexus / Tapatalk 2
[Android Apps and Games] rcfcyl:
Thanks for the quick reply. I'm going to try and fix the light sensor by fixing permissions and possibly flashing a few other ROMs. If that doesn't work, fortunately my device is still in the 1 year warranty period so I might try to get it replaced/fixed. I'm worried about how notoriously bad Google customer support is though. Anyways, I hope to see the camera update soon to fix the min brightness reading issue. A quick question: will using the camera as a light sensor negatively affect battery life?

Again thanks for your app, I really appreciate the effort you've put into its development.
[Android Apps and Games] kantjer:
In store purchase didn't seem to work at first, but after a uninstall - reinstall the Tasker support was in the list of purchased items.

Thanks for this. :good:

EDIT: I cheered to soon, Tasker purchase isn't in the list of purchased items anymore

EDIT 2: after clearing app data the Tasker support is back, but the next time I open the app it's gone again

Look at attached screenshots they where taken about 15 sec apart.
[Android Apps and Games] CHEF-KOCH:
Version 2.00.59 seems to run good for me, all new functions seems to work well. In-app billing seems also good.

But i found that in the newest string.xml some strings are missing.

E.g. from in-app store - Developer support -> "If you find this app cool, any donation is most welcome. No benefits associated." isn't translatable because of the missing string.

And maybe we can adjust the billing debug log showing on the ground under purchased items. I mean velis.vab.dev_support: xyz text. A clear text if you have buy it or not would be better. Or remove it complete because if we buy something it should be listed under purchased items, if we have nothing bought there's noting to list.

I will make a donation later this day or the end of the week. Good work my friend! :good:
[Android Apps and Games] velis74:
Of course i will attempt to minimize impact on battery, but using cameras does take some juice. We'll see...

About store issues: i will try to fix the issues asap. Google doesn't let me buy my own products so i need to create a fake account to test this. I thought i fixed them all, but apparently that's not the case. Muchos trouble to test this functionality :(
[Android Apps and Games] kantjer:
You how to contact me if I need to test something.
[Android Apps and Games] Pkt_Lnt:
My purchase still shows in the app today, no issues.

Galaxy Nexus / Tapatalk 2
[Android Apps and Games] velis74:
2.00.61 (26.10.2012)

Fix for in-app billing

Updated translations: german

This time still only on XDA first post. Should fix issues with app not remembering the tasker support purchase.
[Android Apps and Games] kantjer:
Problem is solved for me thanks for the quick fix.
[Android Apps and Games] RovG:
Greetings All,

In-app store working for me. :)

Text under icon fixed. :)

"Track light in graph" is turned on by itself when re-entering the app. :(

Screen Caps

Spoiler content hidden.
[Android Apps and Games] RovG:
Difference between lux reading using sendor test in *#0*# & VAB.

Screen Caps

Spoiler content hidden.
[Android Apps and Games] RovG:
Hi Velis,

This post is interesting:http://xdaforums.com/showthread.php?p=33255216

It will explain why lux value may seem to be stuck at 10. You may need to read the light sensor values multiple times on screen on to get the correct value.
[Android Apps and Games] velis74:
Thanks for the info. That post really was interesting. However, I read the sensor as many times as the OS sends it to me. Perhaps this will be solved for you when I release Sony Xperia support because that will work by reading kernel sensor data, not by android sensors.

Since I finally released the in-app billing, I'm now finally (again :) ) done with administration and can go back to some real development. I'm doing that right now - so expect some new functionality soon :)

BTW: 2.00.61 is now released to the market.

Edit: Manual updated with Tasker / Locale support info
[Android Apps and Games] MrMastodon:
In app store working fine, a couple of dev support heading your way :)

SGS2, RR 3.1 0 - Dorimanx 7.4.1
[Android Apps and Games] sonwon:
Will reading from the kernel for light sensor level apply to all phones or just from the Sony Xperia? I wonder if this maybe fixes my phones light sensor problem when charging.
[Android Apps and Games] RovG:
Is four presets the max?
[Android Apps and Games] velis74:
The planned support is such that you will be able to enter the path to your sensor readings and the app will take care of the rest. So yes, it will support any phone which has light sensor readings supported this way.

Edit: Thanks everyone for the donations. If this goes on, I will have the expenses covered in a few days :)
[Android Apps and Games] velis74:
No. The preset buttons are scrollable horizontally.
[Android Apps and Games] RovG:
:eek:To prevent silly questions from idiot me, may I suggest that you add some arrows either to the right or left if there are items to scroll. This should make it a bit more intuitive and save me from making a fool of myself:D
[Android Apps and Games] velis74:
This is a string entered directly into google play interface for the app. Once I have more translations, I will add languages for google play as well. Then I will use the strings that are used in-app instead of this "custom" one. So in fact what you translated will be sufficient.

You're not making a fool of yourself. However, I used a standard Android widget for that which unfortunately doesn't exactly make it obvious that it's scrollable. To be honest, I was hoping that it would be obvious when the user saw that last button was getting cut off... Perhaps I should explain this in more detail in the manual, but then again - who reads manuals anyway? :D
[Android Apps and Games] sonwon:
Suggestion, shorten the control on both ends and make an icon appear when the control is scroll-able.
[Android Apps and Games] rcfcyl:
Feature request: is it possible to make your app start in the background automatically on reboot?
[Android Apps and Games] velis74:
It already does that. Check under running apps.
[Android Apps and Games] velis74:
2.01.64 (30.10.2012)

Added links to manual and changelog to app menu

Screen_on sensor override value (going from light to dark room)

Smoothing override setting (when light change is too big, it will just skip to new value)

Setting to update system brightness setting

Fix for proximity sensor action

Fix (hopefully) for graph remaining stuck at some reading

Better logging (long-press proximity reading values to set level 0 - 9)

Manual graph editing as text

Added display of changelog at program start

Updated translations: slovene, german

Added language: hungarian

Are there too many settings now? I have something prepared to counter that, but I'd postpone it in favor of other features if current settings complexity isn't too high.
[Android Apps and Games] CHEF-KOCH:
If you ask me, no! But if you ask me about the other (www) thinks? Yes! There are too much links to your blog or changelog and manual.

I think it's better to store this in the "about" dialog.

And i wondering why there is no option to discard the changelog on app update, because i don't want to see the changelog (btw not "change log", it's one word -> changelog) each time i update the vab app, I can already see the changes here, in play store, on your blog ... (it's too much). "Do not show changelog again" or something similar option under the changelog dialog would be nice.

Sorry, it's not fixed for me. If i flash another kernel, or update my rom i need to reinstall the app or must play with the settings to get it working again (and the vab itself doesn't start as system service).
[Android Apps and Games] velis74:
Perhaps you're right. I just wanted to add link to manual somewhere prominent so the changelog kinda tagged along. Perhaps it would be better to put that into the about dialog.

Changelog should show only once per update. That's why there's no option to discard it. Of course you see the changes more, but the average user only sees this changelog popup that shows once the app is updated.

So this is how I thought this would work:

1. On update, user sees the changelog dialog

2. When desired, they can go to changelog blog entry (because there's no way of displaying the changelog dialog again)

3. For XDA users, they see the release post as well

Please set log level to 9 and send me a logcat of that.

Hmm, will have to look into this. I certainly register for the notification and act upon it. Do you have app installed on SD card?
[Android Apps and Games] aci:
Battery drain of 49%?

Hi Velis74,

I really like your app. However, I seem to have a battery problem as your app seems to be responsible for about 50% of the overall battery usage (see screenshot below).

This is an HTC DesireZ running cyanogenmod 7.1 (Android 2.3.7). The screen was turned off most of the day.

I am wondering if I am the only one with this problem.

Thanks in advance for any feedback on this.

Best regards,

aci
[Android Apps and Games] :
Neither system or BBS even register the app for battery use its usage is that minor. Have you tried a reinstall just in case?
[Android Apps and Games] velis74:
A catlog @ log level 9 should reveal if there is any actual activity going on while screen is off. I know i'm running a safeguard once a minute, but that should not have much of an impact.

About the boot service run: i have checked that and the intent comes through just fine. The app must not be installed on sd though because sd isn't mounted at that time yet.
[Android Apps and Games] polobunny:
Something isn't right with your battery graph if it only shows 4 apps over 14 hours, and 49% Android OS and 49% Velis AB.
[Android Apps and Games] Pkt_Lnt:
I think it is fine. I would like more explanation and/or recommended starting values on the two new additions:

Screen_on sensor override value (going from light to dark room)

Smoothing override setting (when light change is too big, it will just skip to new value)
[Android Apps and Games] cukierkas:
velis, great job with the last update.

proximity sensor works just fine, no sudden backlight changes in landscape mode when sensor covered

bravo!

screen pre_turn_off_brightness is still to go :)

good luck in development, take care of new baby, regards
[Android Apps and Games] polobunny:
Digging the manual edit. Finally my graph doesn't look like a little roller coaster haha. Good job once again!
[Android Apps and Games] SahilC:
Hey, just tried out this app. It's a little confusing for me how to use the graph. Is there a tutorial or something?

Am I being stupid?

Should I be reading through this thread? Sorry;P
[Android Apps and Games] :
Answer all questions yes.

Look in settings for manual link/read the op. I mean come on seriously?
[Android Apps and Games] supergaijin:
I like the manual editing of the graph. took a minute to figure it out, but it's not too complicated. other than that, I mirror pkt_lnt's sentiments about clarification on the screen_on sensor override. I don't know what points it's referring to, and how much of a difference in brightness is needed to effect this command.

@ pkt_lnt, the summary you provided on the sensor override is clear enough. if you're not understanding the summary, remember this: the "smoothing" was the 5+ steps in brightness change when a new setting is applied (brightness of screen increases when the place you're at gets brighter/dimmer). notice how it would gradually get brighter/dimmer? the smoothness override is an instantaneous jump, like if you go into your settings and immediately adjust the brightness from full bright to full dim. there is no gradual change; it happens all at once. that's the smoothness override, as far as I would guess. I haven't tested it, though ;)

from the app, from the first page of this thread, and from the market, you should be able to get to the manual. I skipped most of the middle of this thread, as I assumed there's more comments from users than development information there. most of what you need will be on the first page and in the manual.

======================================================

a quick summary of instructions for manual editing of the graph:

looking at the automatic graph, and applying my understanding from another app I use for rightness control, all phones have a display brightness range from 0 to 255, with 0 being 0% brightness (fully black), to 255 being 100% brightness (maximum brightness for the phone). any number value between that can be calculated based on this range.

1) a sample selection of manual points are provided by default. I deleted most of them, as I did not want a gradual increase and my automatic curves were messed up.

2) each point MUST start with "Pt: " (without quotes, and the space between "pt: " and the numbers must be present for each setting).

3) the two numbers after the point marker are the light sensor's lux reading and the display's brightness. so, for Pt: 0 25, in full darkness (no light), the phone's brightness would be set at 25/255, or about 10% of the phone's maximum brightness

my current manual points (to be revised as needed) are:

Pt: 0 25

Pt: 199 25

Pt: 200 55

Pt: 500 100

Pt: 1500 100

Pt: 4000 200

Pt 17000 200

the first two points, in green, tell the app to keep the phone's brightness set at 25/255 all the way from 0-199 lux.

the next point, in yellow, tells the app that if brightness reaches 200 lux, change the brightness to 55/255.

the next two points, in red, tell the app to keep the phone's brightness at 100/255 all the way from 500-1500 lux.

the last two points, in blue, tell the app to keep the phone's brightness at 200/255 all the way from 4000-17000 (infinity) lux. I'm sure the phone's sensor won't read up to 17000 lux; I just set it at that for cosmetic purposes so the graph is complete.

I have attached a screenshot to show my results.
[Android Apps and Games] SahilC:
Wow. Sounds great Thanks a lot! :D sorry for not reading more.
[Android Apps and Games] velis74:
The red bars have handles at one end. Move them around to change graph.

I would be interested to know how YOU thought the graph should work.
[Android Apps and Games] velis74:
Wow, gaijin, you really took some time with that post :D

Your assumptions and conclusions about the settings are pretty much spot on. Sorry for not updating the manual yet. Perhaps i will have some time tonight since the baby already declared she'll be up most of the night :)

Two corrections:

1 - as you can see from your main screen, your sensor tops out @ 3000, so it most definitely won't be reaching 15000. Your last two points won't ever take effect because you won't get a reading of 4000 (at least i'd assume that from android sensor documentation)

2 - initially i thought that the actual brightness range is 0 - 255 as well, but as it turns out it's just the system settings dialog which imposes these limits. The actual range is a 0 - 1 real value, which is then translated to hardware illumination by driver. By the time i figured this out, graph and everything already worked so i left the values in that range. It's precise enough anyway...
[Android Apps and Games] velis74:
Manual updated with latest settings and screens