I seen it mentioned, but the only time I have seen this was in custom ROMs, usually CM based.
They made it seem like it could be done on a stock phone. If so, how?
Not even really sure what you mean..... why would you want to adjust the auto-brightness? It adjusts itself automatically.
In CM.. you can adjust the light levels depending on your personal preferences.
Some people thing that the auto brightness is too dim, others think it is too bright.
So ROMS like CM allows you to adjust these things, so the auto brightness works how you want it too.
Not gonna happen till we get a custom kernel.
I didn't think we could... but how they said it made it seem it was so.
No worries, didn't need the feature, but was curious.
Related
I want to get back to Screebl this fall and roll version 3.0. I'm going to focus on updating it to make it more 2.3/3.0+ friendly, and try to spend some time on dealing with the variety of issues that come in the form of "I've installed my own custom ROM on my toaster and Screebl doesn't work", which may mean simplifying things a bit. But I digress.
You guys at xda are the most demanding, critical, unrelenting, inflexible, opinionated crowd that I know of. You're also pretty smart. I'm curious to hear what those of you that use the app want to see in a 3.0 release.
dk
Surprised no one has chimed in here yet. First off I would like to say that Screebl is easily my favourite app, even though I mostly forget it is there. Whenever anyone new to Android asks what apps to install, Screebl is at the top of my list. OK, now that the brown nosing is out of the way...
Note: I have a Samsung Epic, currently running the latest leaked build of GB (EH06 as of writing this).
I would like some clarity on the interaction of Screebl and docks. For some reason I can't seem to figure out if it is ever enabled/disabled correctly while docked.
Ever since I started running GB leaks, Screebl has shot to the top of the battery consumption list. This may not be a Screebl issue, but instead something to do with how GB measures battery performance?
I would be nice to include the option to control time between screen off and screen locking.
A slider for choosing the maintained screen brightness, and/or the option to set it to the phone's default.
The option of a 'night mode', with different settings for maintained screen brightness and screen timeout.
Different settings for timeout while on the lock screen vs homescreen vs apps.
Glad to hear you'll get back to this app soon.
Since I updated my Galaxy S to 2.3.4 it stopped working.
I was so sad about this. Now my phone always turns off the screen without me wanting it to..
Wish you good work on it.
Peace
I have a couple of D2Gs running Gingerbread, since the update to Gingerbread the greatest consumer of battery life is the Display, I regularly see 40-60% usage and often only minutes of actual time on.
It seems to be a conflict between the built-in auto brightness and the Screebl low brightness setting. Low brightness is great except when you pull the phone out of your pocket and need to see something at midday...
I discovered that the Juicedefender brightness control manages to keep the brightness at a super low level most of the time, but still auto brightens the screen when required in bright light.
I guess my feature request would be either to have an option to completely remove the brightness control or to take it over with a system that keeps it on minimum brightness but with an user controllable setting to auto increase the backlight when the light sensor detects a particular value.
Thanks for a great app!
I need to update the docs and settings descriptions, but choosing "min brightness" will defer to the phone's sensor generally. That's what I use on my phones.
Dock stuff has been flaky and needs some revamping. I'm planning on redoing the entire loop and eventing framework for the app. It's gotten crazy complicated with all of the device-specific tweaks and conditions involved.
Support for custom lockscreens would be nice. E.g. disable Screebl when MiLocker is in the foreground. Had to stop using Screebl since I started to use MiLocker becuase I can't stand the stock ugly lockscreen.
Just wanted to give those of you that registered interest in Screebl 3.0 a heads up that I've done a ground-up rewrite of the app. It's in beta now -- not pretty, but the underlying engine should be better in many ways, including:
- more compatible with a larger number of devices (moved the accelerometer usage to more modern APIs)
- better with respect to power consumption
- simplified, removed some of the functionality that just didn't work well (like stillness detection)
Still lots of work and polish left to do, but if you want to play with the latest engine, take a look here:
https://market.android.com/details?id=com.keyes.screebl.beta
Let me know what you think!
keyesdav said:
Still lots of work and polish left to do, but if you want to play with the latest engine, take a look here:
https://market.android.com/details?id=com.keyes.screebl.beta
Let me know what you think!
Click to expand...
Click to collapse
I just tried Screebl Beta, and noticed that the proximity sensor is always on, even though the checkbox for it is not checked.
They way I can tell, is that with one of my old phones, the proximity sensor actually glows a faint red light when it's on. To save battery, shouldn't the sensor be off if the checkbox is not checked ?
Firstly, let me say thanks on producing a great app. Always my first installation on any new device.
I've had a small issue on my nexus 5, running 4.4.2 where screebl lite and screebl beta keep turning themselves off. It happens roughly once a day and I have to go into settings and re-enable screebl. Its only a niggle, and not worth uninstallation thankfully.
Good luck on Version 3. :victory:
I have the i717 from rogers and currently running the cm9 official rom but it doesnt seem to matter what rom im on I see this werid fluttering brightness thing occurring on any rom. Try my best to describe it, it is like its almost fluttering up or down in brightness levels when about to dim or undim I am wondering if this is maybe a hardware issue with my device that I should get serviced or if it is normal?
bradtn said:
I have the i717 from rogers and currently running the cm9 official rom but it doesnt seem to matter what rom im on I see this werid fluttering brightness thing occurring on any rom. Try my best to describe it, it is like its almost fluttering up or down in brightness levels when about to dim or undim I am wondering if this is maybe a hardware issue with my device that I should get serviced or if it is normal?
Click to expand...
Click to collapse
I was going to ask what rom .but then had a thought regarding the light sensor on the device .
And I remember reading about sensor calibration and possible causes of fluctuations .
I suppose a search would find that for you ...but check this also ...
Display settings in cm allow light to decrease ...it's a hysterisis setting ...(I butchered that word )
And the settings control flicker in the display . You might try turning those off .
Next is the power saver settings which allow a light decrease also ..after a few seconds of no screen touch ,the light level drops too save power .
And third ...turn off your automatic light level setting in display settings .
I'm thinking three items are conflicting a bit and some mild tuning will fix it ...g
How can I disable or avoid the android setting that makes the brightness go down to minimun when the phone goes to 5% battery?
I have an extended battery and it is very annoying. Maybe I can override the effect with a tasker profile or something?
I'm no expert so I don't know where to start to find any solution...
Anyone?
I tried with a tasker profile but it does not work when battery is under 5%... is there a script to stablish any brightness level?
I am interested too, I didn't have this problem on 4.1.2, but after I flashed 4.3 I encontered this issue.
Very annoying if it happens on sunlight, it makes impossible to use the phone!
I could partially fix it with the app "rootdim" on the Play store, with it I can force it but when the screen goes off it resets again
As far as Internet resources go, this is impossible on Android and is a limit imposed by the kernel.
My thoughts: maybe this is changeable with a build.prop tweak, or a custom kernel. There isn't even an Xposed mod available for this, nor is it included in Gravitybox, Wanam Xposed, or any other collection. I hate this limitation too, especially in the sunlight like @dabyd64 said. You can possibly try using an android shell something like "print 1 > /sys/class/display/brightness" or something like that. Depends on device! I will look into it.
All the best,
aarongillion63 said:
As far as Internet resources go, this is impossible on Android and is a limit imposed by the kernel.
My thoughts: maybe this is changeable with a build.prop tweak, or a custom kernel. There isn't even an Xposed mod available for this, nor is it included in Gravitybox, Wanam Xposed, or any other collection. I hate this limitation too, especially in the sunlight like @dabyd64 said. You can possibly try using an android shell something like "print 1 > /sys/class/display/brightness" or something like that. Depends on device! I will look into it.
All the best,
Click to expand...
Click to collapse
That is what rootdim does, at least you can use the phone, but you have to force the brightness each time you unlock the screen
It has a nice preset widget, so its almost fixed. Single touch and brightness restored.
I think the low brighness is forced because in old roms the screen would flicker if the battery was very low and the brightness set high.
So Samsung fixed it in the hard way
I want to reduce my screen brightness to 5%.
How can I do this without using any apps?
I try to reduce brightness from sys/class/..../brightness
It didn't last very long
So plz help me
Confused by your request. Don't you have a Display section in the Settings to control that?
es0tericcha0s said:
Confused by your request. Don't you have a Display section in the Settings to control that?
Click to expand...
Click to collapse
I mean that, my minimum brightness is 20 I want to reduce it to 5
Sounds basically unusable, but different strokes for different folks and all that. What's wrong with using an app method? You might try and adapt this guide http://forum.xda-developers.com/showthread.php?t=1576356 keeping in mind that where the stuff is at might be different depending on the phone and update you're on. Keep in mind you'll probably have issues installing apps at that brightness. Have seen it before when people are using methods to lower the brightness beyond normal - the install button is greyed out.
es0tericcha0s said:
Sounds basically unusable, but different strokes for different folks and all that. What's wrong with using an app method? You might try and adapt this guide http://forum.xda-developers.com/showthread.php?t=1576356 keeping in mind that where the stuff is at might be different depending on the phone and update you're on. Keep in mind you'll probably have issues installing apps at that brightness. Have seen it before when people are using methods to lower the brightness beyond normal - the install button is greyed out.
Click to expand...
Click to collapse
I will give a try. it kinda confusing
Yea, messing with Smali is difficult for beginners and many non beginners. Heh Using an app will make life much easier and much easier to revert settings if needed.
its not working.
I'm in kitkat
files and code r not the same anymore
do u have anythin like this for kitkat?
I bought a Honor8 a few days ago and while its a great phone, one of the best that was in my hand really, but truly annoys me that the brightess falls randomly.
As i read the threads about this problem it made me sad that as it seems Huawei doesn't really solves the problem, maybe they doesn't care about it, or just cant solve it, who knows...
I tried to search apps for brightness rate fix, or something like that, but didn't find a solution yet.
Maybe someone could write an app for this? Somekind of a background app that you set up a brightness rate and when it falls it automaticly takes it back to the level that fixed?
It would be better than nothing really.
If I understand correctly, you need an app that could adjust brightness based on the available light. And your complain is that stock EMUI doesn't manages it efficiently.
Well no problem, you can use Tasker to achieve this. Even though Tasker is paid, it is well worth the money. If you go with Tasker, reply here and I will send you a profile that could manage your brightness levels more efficiently.
hackslash said:
If I understand correctly, you need an app that could adjust brightness based on the available light. And your complain is that stock EMUI doesn't manages it efficiently.
Well no problem, you can use Tasker to achieve this. Even though Tasker is paid, it is well worth the money. If you go with Tasker, reply here and I will send you a profile that could manage your brightness levels more efficiently.
Click to expand...
Click to collapse
Could you send me a profile please?
Matthias
hackslash said:
If I understand correctly, you need an app that could adjust brightness based on the available light. And your complain is that stock EMUI doesn't manages it efficiently.
Well no problem, you can use Tasker to achieve this. Even though Tasker is paid, it is well worth the money. If you go with Tasker, reply here and I will send you a profile that could manage your brightness levels more efficiently.
Click to expand...
Click to collapse
Sorry, my english is not the best.
Not really, it's nothing to do with the available light or tasking. I do NOT use auto brightness, NEVER, so it should be on a fix rate until i manually adjust to another rate.
But when you start Chrome -for example- the system takes the screen's brightness down by ~20%. Sometimes it doesn't, sometimes it do every 3 minutes when you use chrome. You can take it back in the system MANUALLY, but it'll take it down again randomly, nobody knows why.
So the app i would need that for example: i fix the screen brightness rate to 100% in the app.
Then when the system takes it off the brightness to ~80% -> the app detects it, and automatically takes it back to the rate i fixed in the app before. And should do it in the background without a question or anything.