I'm currently on 2019 june security patch, stock rom v10.3.3.0. Not planning to upgraded anytime soon bcos there is no bug i,ve encounter while using this version and battery life is great. But the lowest brightness is too bright and to blinding during the night. If i'm upgrade to the newest android 9 stock rom using fastboot, does this lowest brightness is fix? How about in android 10? Is it better? Need a quick answer cause this phone is going to make me go blind!!...
Search Google play store for "super dim screen" and try one of the apps, there were at least 2 which worked with this phone, but don't recall which ones exactly.
Or install this testing build of VAB and use super-dim option - https://forum.xda-developers.com/showpost.php?p=83909269&postcount=2224
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:
Hey,
Updated from 4.2 to 4.3 hoping it was a glitch with 4.2 but my screen brightness flickers up and down what appears to be about 5 levels consistently (very fast, resembles a flickering) whenever the display is on. The brightness control also doesn't work, it has no effect on the brightness levels, you can slide it from one side to the other with no actual change.
This has an ill affect of draining the battery about 1% a minute when the display is on.
Anyone have a similar problem or know how to fix this?
I have the auto brightness unchecked and when enabled there is no change either.
xclaw said:
Hey,
Updated from 4.2 to 4.3 hoping it was a glitch with 4.2 but my screen brightness flickers up and down what appears to be about 5 levels consistently (very fast, resembles a flickering) whenever the display is on. The brightness control also doesn't work, it has no effect on the brightness levels, you can slide it from one side to the other with no actual change.
This has an ill affect of draining the battery about 1% a minute when the display is on.
Anyone have a similar problem or know how to fix this?
I have the auto brightness unchecked and when enabled there is no change either.
Click to expand...
Click to collapse
When you flashed to 4.3 did you do a wipe? Have you tried a reset at any time? If you just updated without wipe it would have retained any previous settings or conflicts that may cause this.
Sent from my C6833 using XDA Premium 4 mobile app
I'll do a quick backup and then try a wipe to see if that clears it up. Thanks for the suggestion.
maybe you has to sent to service central but before just update again ,hope will fine
Did all the wipes and no go, called up Bell and have her going in for a RMA check. Can't wait to see what they say.
xclaw said:
Did all the wipes and no go, called up Bell and have her going in for a RMA check. Can't wait to see what they say.
Click to expand...
Click to collapse
Are you sure you flashed the device correctly and followed the procedures in LordManhattan's guide or [NUT]/blueether's posts?
I just installed Jasmine 9.1 on Friday. It's working great, but I noticed that the screen is really dim at night when set to auto-brightness. I was driving home from my in-laws' place on Saturday night and had Waze running. I switched my phone to auto brightness and had the slider up at 100%. But then the screen faded to an almost unusably low brightness. It was completely dark in the car and no one was behind me. So I'm sure the lux level in the car was near zero. I ended up going back to manual brightness and set it to about 50%, which was fine for the drive home. But with prior versions of Jasmine and CloudyG3, the auto-brightness never got that low at night.
I'm not sure if this is a Jasmine issue or a 5.1.1 issue. But I was curious if anyone else has noticed it or has a fix. I just reset a bunch of auto-brightness settings using GravityBox, but I'm not sure if they'll take or not.
I've noticed that 35B (both 100% stock and rooted) is dimmer on auto-brightness in slightly dim environments. It's not specific to Jasmine since I was on 100% stock not rooted for a week or so before the downgrade TOT method was tested so I could root again.
I'm afraid I haven't tested any third party solution to this problem yet, but just wanted to confirm that you're not alone. I've been turning auto brightness off more often because of it.
I figured it was my eyes just getting older!
That's what I've been doing. Even in complete darkness, the dimness is too much so I turn off the auto brightness.
Having same issue with Sd6.0.2
I installed lux lite from the play store. Have it set to auto and it handles the auto brightness much better than stock. Going to play with this for a few days.
rswain64 said:
I installed lux lite from the play store. Have it set to auto and it handles the auto brightness much better than stock. Going to play with this for a few days.
Click to expand...
Click to collapse
Any suggestions on specific settings for Lux?
I'm using dynamic with day setting and automatic. Seems to work good for me. I'm constant going from inside to outside and don't have to mess with the brightness on these settings
Hi guys,
I'm in love with my Honor 9 (and with my girlfirend obviously, she's standing right there when I'm writing this post ) BUT there are some issues.
1) The auto-brightness isn't working as it should. Previously I had G3 and the auto-brightness was amazing but with Honor 9 it seems to do whatever the phone wants or what. I'm outside on the sunny day, want to take some photos but the screen is on it's minimal brightness and reacts very slowly or not at all and when I move the slider to the point of max brightness the screen is still darker than it should be (I got the max brightness when I turn off the auto-brightness only). Overall the auto-regulation is sh*t. Do you have the same issue?
2) From what I found this is a well known bug with auto-brightness. The screen is dimming when I open some apps like GMail, Chrome etc. and it's really annoying. Overall the brightness is wierd and even with the auto-regulation off and display on max brightness is dimming sometimes. This should be problem with the EMUI 5.x so I have three questions. Do you have the the same issue? Does B130 solve this (I wasn't lucky to install it and now I can't find it, phone says B100 is the most recent version - they stopped the update?)? Does any of custom ROM's solve this?
Thanks a lot.
I'm on stock ROM B100, EU version, CZE.
That happens with almost any Honor device with nougat (EMUI 5)
In other words, they don't give a fu*k right?
It seems so
Thought so. Can it be solved with other ROM?
I don't know, I've never tested a custom ROM on honor 9
The recent FunTouch OS 12 has a lot of features missing. It feels like IQOO has rolled up the updates in a hurry.
1. No Android 12 Clock widget.
2. No Quick Panel tiles like Android 12.
3. Dark mode not getting applied on App Drawer.
4. Etc etc
Bloody hell, when will we get Origin OS for Indian market.
This device has so much potential if they just unlock the bootloader for installating custom roms
Disabled animations in Developer menu doesn't get applied either
Also, home screen is not coming from many widgets like the one we get by swipimg right from left edge
This seems like an Alpha version without much testing and stitching with animations quite annoying like dark mode not applying to app drawer
This is almost the the first few versions when we bought the device during launch. Only after one June or July upgrade things became like a release version. Established that IQOO OS team for IQOO 7 releases updates without proper testing and going through beta testing as such issues were never encountered in IQOO 3 with IQOO OS which people for some reason criticize
Witnessing huge flashes of brightness fluctuations at night even when automatic brightness is turned off.
Still can't find a way to switch off Accessibility button
Prankey said:
Witnessing huge flashes of brightness fluctuations at night even when automatic brightness is turned off.
Still can't find a way to switch off Accessibility button
Click to expand...
Click to collapse
Same here. Gets blindingly bright in the middle of the night. My phone also keeps crashing atleast 3 times a day. Waiting for a fix update.
abnormalindian said:
Same here. Gets blindingly bright in the middle of the night. My phone also keeps crashing atleast 3 times a day. Waiting for a fix update.
Click to expand...
Click to collapse
Yup, same here as well. Plus sometimes when I enable battery saver the brightness also increases even if auto brightness is turned off and manual bright is set to lowest possible value.
I still have similar issues on my Vivo X80 Pro and many familiar features like the new Control Center are still missing! What shoud that? OriginOS would be so much better, why do you have to develop such a bad operating system internationally. I don't get it and I'm actually very, very excited about the X80 Pro but the software totally ruins the experience!