Related
can someone please tell me how to disable auto brightness on
x10i eternity rom build 003
i tried using every brightness app/widget possible to turn it off but as soon as i turn it off and put the phone under different light setting i can see that the auto brightness is still on
i tried using adjbrightness but it keeps telling me that my phone isnt rooted; anyone get this app to work on x10??
please help n sorry if this questions been asked and answered before. this forum is getting too big and broad sometimes to find anything
thx in advance
Have you tried Sparepart? (That's the name)
Strange, i can't seem to turn on my autobrightness. It used to work perfectly in android 1.6. And i haven't noticed it untill recently. When auto brightness is checked, it just stays the same, even when i hold it directly under a lamp. Maby there is a bug in the software that prevents switching it on or off?
I'd also like an answer to this problem, because with auto brightness on the telephone is a battery eater.. you have to keep it to the minimum level to disable it, but when you are under a strong light, like outdoor with a sunny weather, it's difficult to see your screen's details. as you select a brightness level different from zero, the autobrightness turns on and eats the battery.
I hope I'm missing the solution to this, and somebody will help, because all the applications i've tried (spareparts included) didn't worked.
I'm quite confuse now.....
What actually do we need......
Turn it on...
or
Turn it off...
LOL
heh, so some people want a way to turn it off and others, like me, want to find a way to turn it on?
what a crazy phone..
I'm sure there used to be a tick box in the display settings to turn on/off the auto brightness. Anyway, i've tried various applications myself to get it on but nothing does it. I think the best solution is for us all to swap phones .
Spare Parts doesn't work for me, i tried enabling it, restarting the phone and jumping under my duvet.. but it didn't change
Did you update to 2.1? It was disabled in 2.1 as far as I know.
So the easiest solution, upgrade to 2.1! Else, I don't remember the menu but it's somewhere in the settings under 1.6.
I think we've all updated to 2.1 here =)
and yes, in 1.6 there was a box to tick to unable/disable autobrightness.
But, in 2.1, this feature has disappeared, leaving a seekbar and a damned widget which doesn't allow you to set or no autobrightness.
Hi,
The autobrightness is still there. It can be turned on/of from a stock SE connection widget. The different state for brightness is "minimum" -> "auto" -> "maximum"
MxCraft said:
It can be turned on/of from a stock SE connection widget. The different state for brightness is "minimum" -> "auto" -> "maximum"
Click to expand...
Click to collapse
Thats pretty much, exactly, what dpk0875 said, if i'm not mistaken.
As soon as i turn it off and put the phone under different light setting i can see that the auto brightness is still on
Click to expand...
Click to collapse
I can get, either 0%, or 100% brightness, with the ambient sensor disabled. Anything in-between, fades constantly.
No fix for this, i presume?
Reading websites while the screen fades in/out every couple of seconds drives me mad.
Ive never had any problem with it as long as you dont lean in front of it all the time lol.
Sent from my X10i using XDA App
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:
So after some research and Googling, I discovered that "Killling" your app is only worse or has no effect for your battery life. Even using apps that "save" battery only harm it even more. I've been told these were the fundamental things to save battery ever since I even got my hands on a smart phone.. Guess I've been asking the wrong people.
So, what are real ways to save battery? I'm a heavy phone user, often surfing the net or watching Netflix on the go. Dimming my screen is not enough, are there any other techniques to prevent my phone from dying? I've got an Android 4.
If you're rooted:
Underclock
Undervolt
Change cpu governor/io scheduler
Flash different ROMS and kernels
Change your modem
And a few more.
Not rooted:
Use screen filter? Lol.
Update your firmware
Sent from my GT-I9100 using XDA
okmijnlp said:
If you're rooted:
Underclock
Undervolt
Change cpu governor/io scheduler
Flash different ROMS and kernels
Change your modem
And a few more.
Not rooted:
Use screen filter? Lol.
Update your firmware
Sent from my GT-I9100 using XDA
Click to expand...
Click to collapse
I am rooted, thank you for the info! I'll be looking into it~
Get bigger battery?
Turn thing off lol only kidding but turn off auto updates such as news etc
If you look at your battery stats, under settings, you'll see what uses the most battery. Usually I find that my screen uses around 70% of my battery, but if you have something else high on the list you might have a "rogue app" preventing your phone from going into sleep mode.
If your screen is the culprit you can only save 10% or so by throttling your CPU etc. The only way you can make real savings is by reducing screen brightness.
Easiest way to save battery is use gemini app manager to stop apps being able to autostart when you don't want them to as then you don't have the os having to kill off unused apps to make more free ram.
For example a lot of apps can autostart when your wifi goes on or off, when your 3G signal drops etcetera including things like facebook or google play. By changing auto start for such apps you don't have to run a task killer which also saves battery.
Dave
Sent from my LG P920 using Tapatalk
i use the aokp rom milestone 4 atm, and i also have come accross a fantastic battery app called "Badass Battery Monitor". its free and details very very specifically what apps are using the battery most.
I have managed to increase my battery by rooting out the apps i dont use that are using prescious power...
Also, turning off useless app permissions for apps theat really dont need them and work perfectly well without them will also save on power massively. for this i use "LBE Privacy Guard" works an absolute charm
I have widget where I can turn off Internet connection, set brightness, GPS etc. Internet stand-by mode uses damn much battery... And when you don't use Internet, you can put on 2G, it also saves battery.
This may not benefit you if you are a heavy user but I find the feature on my Droid 3 that turns off 3G after 15 minutes of inactivity saves battery and also saves data. Not sure if this is a standard Android feature or if it would even benefit you.
Here with LG P990 and I don't have option to turn off 3G aftre some minutes... but if/when you didn't need high speed you can choose only 2G network (for example when needed receive only notification): this save a lot your battery.
Moreover you can verify battery consumption to see if there are autostart apps from your vendor than have heavy power consumption (for me there was OnScreenPhone) and use gemini app manager as explained previously.
In the end you can find out custom ROM for your device usually optimized for smoothness and power consumption.
First apps I download when switching to a new Rom to get a little control on battery are
Adfree- Get rid of ads, they eat a bit of battery.
DroidWall- Control what apps are able to access Internet under separate "Mobile Data" and "Wifi" Conditions.
Screenfilter- Dim the screen below factory settings.
LED's hack- Turn off the Softbutton Backlights (home/menu/back/search), even though they don't seem like it may eat up your battery, it is an extra 'light' that's on, even though it may be minimal, it's still drawing power.
Also, It maybe just a Photon thing cuz of the Pentile display but I always use if not completely Black background image, a dark one because the 'lighter' or 'whiter/colorful' images take more battery, same reason I always look for 'Inverted' or black themed apps too.
Turn OFF any 'Haptic feedback' settings on your phone (Keyboard, Phone DialPad, Screen/UI Interactions, etc..)
For Calls (Ringtone) and Notification settings, don't have them set to 'Ring and Vibrate' or just 'Vibrate' because the Vibration Mechanism will eat alot if battery. Some may argue that the Notification 'Vibrate' setting and even the Haptic feedback (which does in fact use the phones Vibration mechanism) would not kill battery because it's a 'quick' or 'minimal' use (depending on use) and but if your keyboard had the Haptic feedback on, thinking of how many times your touch the keyboard for even on Text message, try will add up and help kill the battery.
Turn OFF any/all Homescreen/UI Animations
Turn OFF any Auto Sync setting and instead have APPS sync in a specified interval, (Of course Depending on how important the information that's being pulled like Email) , Could be set to like every 4 hours to sync an so on.
Manually input Date/Time settings instead of "Get network provided values" because it'll be one less thing pulling from Internet.
Set Screen Timeout to 30 Secs and Never have Auto-Brightness set, instead use a brightness toggle of some sort (Stock 'Power Control' Widget works well) to only have it as bright as you need to view in current conditions.
Open the Google 'Talk' application and uncheck the 'Auto log-in' setting, and then 'Sign out'. For some reason this always runs in the background and eats alot of battery.
If I think of more things ill post them
Hope these tips help, if they do don't forget to hit the thanks button thanks.
MoPhoACTV Initiative
There are many ways...
Switch on WiFi, 3G at only using, and close the not using application, decrease display brightness etc...
And if you root your phone, you may change CPU governor, or build.prop tweaks, script tweaks... Or change to custom kernel or custom ROM.
I forgot that 'LED's hack' is not available in the market anymore, I attached it below.
i hv just downloaded screen-filter lets c how that works...
Juice defender
Try JuiceDefender by Latedroid. It helps a lot to turn off things you don't need when you don't need them. Sorry I can't post the link- I'm new to XDA
my experience:
undervolting does not help much. you have to test a lot for only a little bit of improvement.
in my opinion you will not really remark it.
but what helps, i think, is set cpu speed, if possible. for example i use samsung galaxy s2 where cpu has max 1200mhz. i set max cpu freq to 800mhz. with a good rom (hydrogenics f.e.) android keeps running smooth with 800mhz and battery lasts noticeable longer.
I agree that undervolting doesn't help so much.
Like in up post, best thing to save Your battery is to change cpu power. You can also use diffrent cpu govenor : good for battery are smartassv2 and power save. Just need to have rooted phone and download app, fx. Antutu CPU Master or Set CPU. U can also make your cpu speed profiles.
Change the minimum brightness level from usual 10 to 1. It doesn't modify the autobrightness level map so automatic brightness won't be lowered (though it can be easily adjusted on CM11).
This is so far exactly the same as GravityBox offers (modifying 'config_screenBrightnessSettingMinimum').
But Minimum Brightness offers one unique feature - it also modifies the lower brightness levels in MX Player (free/paid). Because no matter whatever you use manual or auto brightness, MX Player always uses minimum brightness of 0.05 (12/255, 19/255, 27/255, 36/255...). To actually lower the brightness, you would have to turn off brightness control in MX Player or use one of many 'overlay filter brightness app'.
So Minimum Brightness module retains the same quadratic function for brightness levels but includes lower values (1/255, 4/255, 9/255, 16/255, 25/255...).
Minimum Brightness uses value 1/255 which might not be suitable for every display (meaning LCD) but it suits perfectly my Super AMOLED screens (Galaxy S5 / Galaxy Tab S 8.4) and watching videos at night is still enjoyable.
There are many excellent auto brightness apps (Lux, Darker etc) that can use overlay filters to lower brightness even more so it's up to everyone to try and decide.
This module has been merged into new module http://forum.xda-developers.com/xposed/modules/mod-xposed-tweaks-cm-t3279109. Please check that module for any future updates.
Hello! Thanks for the mod, I will test
Works very nice on Xperia Z2, however minimum brightness is absolute darkness Could you please add an option to define minimum brightness value?
_mysiak_ said:
Works very nice on Xperia Z2, however minimum brightness is absolute darkness Could you please add an option to define minimum brightness value?
Click to expand...
Click to collapse
The situation is the same on my Xperia SP. When I set the brightness to miniumum the screen is totally black, also when the backlight decreases after 10 seconds screen gets black.
Hi! Tried min brightness but when screen is set to the lowest level, I get a white screen after locking the phone.
Sent from my DIAMOND D1 using XDA Free mobile app
Really great tweak!! I'm noobie in Android enviroment with my new Elephone P3000S and the lowest screen brightness is to high for me so your tweak is very usefull.
I also have the issue that the lowest brightness level sets the screen completly black and I have been scared for 1 hour truing to solve a completely black, touching all buttons but the phone didn't "wake up". Finally, pressing power buttom + volumen up + home soft key it has worked :angel:
So it would be very important to prevent black screen by allowing the user to set the minimun level.
Thanks!
Hey, I know making GUI is a pain in the ass so can you please make alternative version with minimum brightness set to 2? That will satisfy most of people complaining here. Your app is currently the only dimmer working on lollipop.
Dri0m said:
Hey, I know making GUI is a pain in the ass so can you please make alternative version with minimum brightness set to 2? That will satisfy most of people complaining here. Your app is currently the only dimmer working on lollipop.
Click to expand...
Click to collapse
I will have a new device soon so that could make me change my mind about lowest value and UI.
@Dri0m
In the first post you can find archive containing multiple versions of module with different low values.
How to disable this module...?
I installed this module last night, enabled it in Xposed Framework, but did nothing with it. Then this afternoon I opened the Settings menu, went to Display, and before I could do anything else I received a phone call. As I terminated the call, the screen flashed, the phone rebooted--and after restarting it is completely, or almost completely blank. If I repeatedly tap the power button I get a fraction-of-a-second glimpse of the SIM PIN screen at normal brightness. This leads me to the suspicion that, by some weird combination of bad luck and an accidental touch of a finger after terminating the phone call, that the Minimum Brightness somehow got set--although why the phone then rebooted I don't know.
Anyway, by luck and good judgement I finally managed to enter the correct SIM PIN and then the phone unlock PIN. However, I can do nothing else. The screen is still blank, and as the phone is currently unlocked I don't want to touch the power button. Before sending the phone back to the manufacturer or anything drastic like that, I would like to try disabling the Xposed Framework. Whilst trying to find something useful in Windows Explorer I found Xposed-Disabler-Recovery.zip in the Internal storage\Android\data\de.robv.android.xposed.installer\files folder on my phone. I assume that this should be what I need. However, as I cannot see anything on the screen I would need to know the exact buttons to press, in which order and how many times etc, in order to enter the Recovery menu and do what is needed. According to the phone manufacturer the OS is unmodified Android 4.4.2., although strangely they will not even tell me which keys to press to enter the Recovery menu (long story, the upshot is, they flat out refuse to help apart from suggesting returning the phone).
Note that I only suspect it is the Minimum Brightness module that is causing the problem, however the problem did not exist before yesterday (when I installed the module), and as I was about to do something with the brightness when the phone rebooted itself, it seems too much of a coincidence to be anything else. If I cannot disable the module/framework, the only other thing I can think of is a factory reset--but again I would need to know exactly which buttons to press, in which order etc. Unfortunately at the moment USB debugging is not enabled, and again without the screen I cannot access it to turn it on.
Any help or suggestions hugely appreciated.
PL
@Papalazzzaru
Xposed now sports a safemode which allows you to disable Xposed during bootloops. To disable Xposed, you'll have to repeatedly tap one of the hardware buttons (Power, Volume, or Home) on your device during startup.
During boot, your device will vibrate twice when it detects the first key press. You'll then have five seconds to press that same button four more times, with each keystroke producing a short single vibration. After ending with a long vibration, your device will disable and prevent most of Xposed's actions, allowing you to easily troubleshoot problematic modules.
Sorted
Outstanding, thanks.
Papalazzzaru said:
I installed thi............. gely appreciated.
PL
Click to expand...
Click to collapse
Device model please?
Caterpillar S50, on Android 4.4.2, baseband version LTE_S0201121.0_S50_0.017.00.
it is compatible with lollipop?
imam88 said:
it is compatible with lollipop?
Click to expand...
Click to collapse
The MX Player part still works. I don't know about the lowest value of brightness in general but at least with CM12 & Samsung the brightness goes to the hardware minimum by default.
Thanks, this is exactly what I want.
Could you make it for LP ?
I want my phone be absolute zero brightness for driving navigation.
Tested it on CM12.1 Nightly on the Nexus 6. It works here, but on 0 the screen is a bit purple. However, I guess this is the screen's fault
Gesendet von meinem Nexus 6 mit Tapatalk
moneytoo said:
The MX Player part still works. I don't know about the lowest value of brightness in general but at least with CM12 & Samsung the brightness goes to the hardware minimum by default.
Click to expand...
Click to collapse
Yes it works
This module seems to be working well on the Moto X Pure Edition (Motorola xt1095) running Lollipop 5.1. It's an AMOLED screen, and I personally find the minimum brightness on 5.1 too bright, so this has helped solve that.
OK so I got my Z4 tablet three days ago. Fantastic construction, fantastic specs on paper.
I had a Z tablet up until last weekend that I sold for a good price and got this as a much needed replacement.
Both are LTE versions.
Anyway, here are some things I've noticed and I would like to have your comments on.
1) The "antitheft" system for the first two days seemed to be a PITA. As my device is set for three users (me, my wife, my son), it kept popping for the others that it locked and needed MY credentials to unlock. I did unlock it at least five times for each, which means I can't really be... far from the device and let them use it. That I use two step authentication, makes things even harder. Once my "authenticator" phone was out of power and I had to wait several minutes to unlock the tablet. Yesterday I updated to latest firmware and I haven't noticed the issue since. But it's just one day, it may come back. Once (before updating firmware) I tried to disable My Xperia (although I love the find my device feature) so they could work, but it kept me "waiting". In the end I pressed back and it didn't get disabled. Any similar experiences with the theft protection?
2) Backlight (set in auto) seems to be too dark some times. I clicked on the intensity bar, set it brighter while STILL in auto (like it is now set to have a brighter "base value"?). Does this sound normal?
3) This is not a Z4 issue, I also had this in Z. It's probably a lollipop thing or I don't understand something properly. Clicking the volume buttons I can set it to "no" sound from home screen. Or so I think. Because even if I set it to "off", apps STILL have sound and I have to RE-adjust the volume to off from within the app (without the "priority buttons" under the volume bar)... Am I the only one to find this stupid?
4) Anybody notices some lag or ESPECIALLY stuck web browser, when other profiles (users) have run apps? If I reset the device and not visit the other profiles, the device is more snappy. If some other user goes in, even quiting every app they run, the device seems to get slower when back in "owner" user. Still fast but not as "snappy". Anybody noticed the same?
5) Any idea when we get Android M? Will we get 5.1 before that? I mean official firmware. Anybody?
6) Is there a way to go to test menu? The tablet Z method doesn't seem to work.
7) Serious. No restricted profiles. Why? Sony support replied that lollipop has this disabled only on 3G/LTE devices (that makes no sense), yet my Z was also LTE and both are on lollipop 5.0.2 and it DID have restricted profiles. What's up with that?
Thank you for your time people, have fun.
...wow
2) Yes.. brightness is usually set a little low at first for battery purposes.
3) There are different volumes for different things. Using the volume rocker on the home screen and putting it all the way down will only adjust ringer/notification volume. In-app sounds will use the media volume which you will need to adjust while media sounds are playing or you can adjust it in your sound settings. Not stupid imo, just gives more flexibility.
5) It'll come when it comes.. nobody knows except google and sony. I'd like to hope we'd get 5.1 before 6.
(pending something on the other questions above)
2) So the set value, when brightness is in "auto" is like a base value?
3) Well I find it stupid. Why: Because when I am in home screen I used to be able to manage the universal audio settings of the device. Turning device to mute, would turn it to mute. As simple as that. Also clicking a simple icon next to volume bar, you could separately adjust notification and ringer and stuff like that. Now? You THINK you set your device to mute, but you have only set the notifications. You sleep in a silent house (next to the wife or something), start a game, it YELLS with the last volume settings, ignoring that you set the device to mute in home screen and you have to "run" and re-adjust the volume to zero, usually with some delay (in the meantime waking everybody) since the device won't let you adjust anything while loading the game. No, I call this stupid.
5) Well if it won't delay 6, I don't mind for 5.1. But I want 6 the soonest possible.