Don't worry about it, I'm updating the market version tomorrow.
I just noticed the CPU issue as well on my Galaxy S3. The poll rate was set to fastest. Was that what it was set to on the old version (before the newest slate of updates? If I have it on fast or even medium, it still keeps my CPU over 50%.Ok, there's a lot of stuff to reply to here, so I'll make some comments:
- The CPU issue is poll rate related. I accidentally hard coded a fast poll rate into the app (so choosing a different rate doesn't change it). I pushed out an update to fix this just now.
Poll rate defines how fast the light sensor is polled for changes. Even the slowest settings is quite fast. The only reason I have it there as an option is because devices with dodgy sensors don't work well with slower poll rates. On the other hand, good devices use too much CPU with faster poll rates. 'Slow' and 'slowest' are perfectly fine for quick updates - perhaps I should have named them something less negative sounding.Could someone help explain the pollrate new setting? What does it do, what is the difference between that and the period check? Is it how quick the check is acted on? What values are the Fastest, Fast etc.
I'll consider this for a future update.Ok, in this case can I ask for just time settings for night mode? Will highly appreciate! Also it will be great to have possibility to link Night mode with offscreen buttons backlight (on/off). Thank you in advance to consider my small request
What are you doing when that occurs?Latest update in the play store gives me an error about no SD card on my Nexus 7.
Yeah I agree, I shouldn't have given people that much control. It was put there for people with bad light sensors to try a higher poll rate, but now it's backfired because people like to touch settings they don't really understand.I just noticed the CPU issue as well on my Galaxy S3. The poll rate was set to fastest. Was that what it was set to on the old version (before the newest slate of updates? If I have it on fast or even medium, it still keeps my CPU over 50%.
Seems like you shouldn't even have an option that would allow someone to set this to take up 50% of the CPU constantly. If I set it to slow, my CPU drops way down to about where it should be while idle.
Did the latest update fix this for you?Could anybody confirm that Manual backlight on call option is working? I can not switch it off. Even with unchecked box this option rule backlight for calls
Отправлено с моего GT-N7100 через Tapatalk
It's working on my end. I'll see if I can try it on an S3.Sleep list isn't working on my galaxy s3. I go to sleep list, then add and it says loading, then it returns me back to the menu with sleep last in it.
Indeed, I'll do it tomorrow when things settle down and I get time to update everything.
Vito - your app has too many permissions. I swear to God that my phone attempted to send all of my credit cards to Rwanda.
Poll rate defines how fast the light sensor is polled for changes. Even the slowest settings is quite fast. The only reason I have it there as an option is because devices with dodgy sensors don't work well with slower poll rates. On the other hand, good devices use too much CPU with faster poll rates. 'Slow' and 'slowest' are perfectly fine for quick updates - perhaps I should have named them something less negative sounding.
Basically, don't make it faster unless you get wacky sensor readings (usually a HTC issue).
I removed filtering from Lux in favour of a less CPU intensive solution (which only applies to dynamic and ascending modes). What automatic mode are you using?Hello,
I have troubles with setting the application on low lighting levels. It just jumps from one level to another and back over and over again, no smooth changes like when I was using stock autobrightness or enhanced brightness in Jellytime ROM.
I suppose it just sets it like:
sensor - level
10 - 20
160 - 40
280 - 60
and it cannot approximate values over certain period?
This permanent flickering is very annoying.
Sent from my Desire HD using xda app-developers app
Samsung probably don't use the Android API to get the light readings, so they don't have to wait for an event to trigger to get data. Lux should be giving you the last detected light value, unless you restarted Lux (or your phone) in an area of constant lux.Will check tomorrow if the manual call brightness is working, now it is night here .
About Samsung sensor not giving data sometimes to Lux, when in Debug section I see 0. At the same time stock auto brightness see very well the level of ambient light:
Here is two screenshots made when in complete darkness lux lost sensor data, stock brightness app see very well the level of ambient light
Отправлено с моего GT-N7100 через Tapatalk
If it can only change subzero values, then your ROM/kernel isn't passing on the brightness values to the display. I use the Android API for this, so it should work fine. Also check that you haven't put Lux into sleep mode (see if it says 'sleeping' in the notification).Hello everyone, I have a problem with this application. It should change the brightness automatically, but for me it is only possible to change with negative numbers (sub) if I link for example - 50% with 0 lux, but between 0% and 100% I see no changes. Can someone help me  I use Cyanogenmodnightly 10.1 in a Samsung galaxy s I9000. Thanks
Inviato dal mio GT-I9000 con Tapatalk 2
Inviato dal mio GT-I9000 con Tapatalk 2
Latest update forces the poll rate to 'medium' (which now has a value between the 'slow' and 'slowest' values in the last release).On my Galaxy S3, it is set to fastest as default. Normal? That might be why earlier users had it like so:
http://i13.photobucket.com/albums/a286/ikjadoon/Screenshot_2013-02-26-23-33-37_zps652bc76c.png
I changed it to slow, as recommended in your pop-up....however, to prevent these types of issues in the future, is there a guide or manual for Lux available anywhere? I could help you write one, if you'd like!
Also, would it be difficult to bring back the alpha settings for night mode? For me, the yellow filter seems too weak. One other poster mentioned this.
Also-sorry, I should have tried the beta-with the previous overlay, changing between manual and my automatic mode was simple, press and hold the circle refresh icon. Now, I have to open that menu, go past options I will likely never change, and tap manual. Do most people prefer the new way?
This isn't unusual for Samsung devices. They all overstate how much power Lux uses. There's also a chance that the high poll rate causes that anomaly, which is now solved.Hmm, today Lux appeared among battery eaters:
Отправлено с моего GT-N7100 через Tapatalk
I removed filtering from Lux in favour of a less CPU intensive solution (which only applies to dynamic and ascending modes). What automatic mode are you using?
Playing with dynamic and ascending. What I am not able to achieve is some sort of constant backlight between 10 and 160 lux reading. Typical scenario: half-dark room with softly-lit lamp by the couch. When I move my hand over the device or just slightly change the angle, the sensor reads 160 for a moment and sets the brightness higher. 2 seconds later it comes back to 10 and the lowest backlight is back. And this repeats every 20 seconds or so.
It seems to me that I can't get analogue curve of brightness, it just jumps between sensor values. Maybe it's normal behaviour but I haven't noticed it with previous roms/brightness tools I tried.
<activity
android:name="com.vitocassisi.lux.plugin.MainActivity"
android:label="@string/app_name" >
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.LAUNCHER" />
</intent-filter>
</activity>
<receiver
android:name="com.vitocassisi.lux.plugin.LuxBroadcastReceiver"
android:exported="true" >
<intent-filter>
<action android:name="com.vitocassisi.lux.plugin.search" />
</intent-filter>
</receiver>
<service
android:name=".[B]MY_PLUGIN[/B]"
android:exported="true" >
<intent-filter>
<action android:name="[B]YOUR_PACKAGE_NAME_HERE[/B]" />
</intent-filter>
</service>
Copyright © 2013 Vito Cassisi
You may not use this library except in compliance with the following:
- It cannot be used for commercial purposes under any circumstances, unless explicit permission is granted in writing from the author.
- Modifications to this library may not be distributed.
Unless required by applicable law or agreed to in writing, software
distributed under this licence is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.