I have the C5J6 model and before upgrading to Mireks roms I was on the stock rom. While on stock my brightness was controllable, ranging from the expected low to very bright. After upgrading to Mirek v6.1 the brightness option was no longer controllable and appears to be at a set position. I can still move the brightness slider, but nothing actually happens. I have just moved up to v7 and the issue still exists.
I have the dual boot model, so to be sure I wasn't loosing my mind I booted into Windows and brightness is controllable and very bright at the highlest level, as I like it. So I know it's definitely related to something with the rom or Android in general.
Is there a fix to this, or something I am missing?
Aside from this Mireks roms have worked beautifully.
Thanx!
I seemed to have resolved this by installing a brightness app which worked on its own and then seemed to restore functionality to the native brightness control.
Related
I upgraded my i896 from ICS 2.11 to 3.1. Everything seems to be working well, but auto-brightness seems to be fixed on the dimmest setting. Previously in 2.11 this was working correctly. Manually adjusting the brightness works fine.
I tried placing the phone under a bright light but it had no effect on increasing the level.
Also, I tried installing the Sensors Fix, but that just resulted in the opposite problem -- the auto brightness was stuck on the brightest setting.
Does anyone have any other suggestions to fix this problem?
Edit: Sorry, I just realized there is a thread specific to ICS related questions. I should have posted this there.
I instaled 254 stock fw and seems like auto brightness is not working. When I chech auto, it just dims screen a little bit and that's all. It was the same on existenZ rom. Seems like it only worked only in CM11. Is that a common thing or is here some workaround?
Coming from Atrix 4G, i found the way the xperia SP handles auto brightness is pretty bad...
So i tried Lux, but it looked like my light sensor was screwed up... always returning 1 or 2 lux.
So i searched and managed to get it working again by installing this tool first, to disable auto brightness:
https://play.google.com/store/apps/details?id=com.hatcyl.android.Disable_Auto_Brightness&hl=fr
Then Lux would do the trick :
https://play.google.com/store/apps/details?id=com.vito.lux&hl=fr
Same here. Auto brightness is just low brightness. Something is wrong with the stock 4.1 because on SlimKat it works well.
pappbence said:
Same here. Auto brightness is just low brightness. Something is wrong with the stock 4.1 because on SlimKat it works well.
Click to expand...
Click to collapse
On Existenze 3.30, which is JB 4.3, auto brightness also is not working (or at least not working as I would expect it to be). So I guess its just has something to do with sony framework or smth.
Stock auto brightness (4.1.2/4.3) never worked properly for me. I'm using 'Velis auto brightness' app. Works like a charm..
So. Recently got my second transformer. After a few hours use it switched off and refused to turn on at full brightness - in the dark i could just just see icons on the homescreen. After a while it seemed to tun on again. Crazy. So i updated to and used latest 4.4.2 stock for a day, the screen was working perfectly at all brightness levels, uniform, no light bleed. Then i flashed a few of the available CM based roms. This morning, a few days in, i notice that the backlight is much much stronger on the right.
At low brightness it was completely ridiculous. Its like one of the rows of leds wasnt on at all. So i reflashed a backup i had from install day and now everything is just fine - uniform brightness, working perfectly. It seems to be a driver bug. But how did it survive me going from kernel to kernel?
So now im wondering if its a hardware issue... any thoughts?
Ive now noticed this happening on a number of occasions to different rows of the backlight - sometimes at bootom, sometimes at bottom and right. Anyone else seeing something like this?
Sounds like hardware to me...
berndblb said:
Sounds like hardware to me...
Click to expand...
Click to collapse
I flashed the latest cm and this seems to have stopped happening so looks like driver issues. However, the screen continues turn off sometimes, and when it does it needs two presses of the power button to turn back on. Its a crazy thing asus - i had the last infinity too, sold it after a few months because it just wasnt as good as my nexus 10. And now this... pretty amusing.
Dunno why i keep buying asus. Must be my good experience with their motherboards or something... usually they also have excellent support and firmware updates.
This is my first Lollipop device after a long time with Kitkat, so I may be missing something obvious, but I just can't wrap my head around Adaptive Brightness.
So when it's set to on it adjusts the brightness based on the light sensor, but I can also use the slider to tweak it, correct? But then sometimes the slider just stops working, moving it doesn't change the brightness at all. Only way to make it work again is to change the lighting significantly (for example I point the phone at a lamp). After the auto-adjustment kicks in I can tweak it with the slider again. Is this a bug, or yet another misguided "feature"? Do I have a hardware problem? I've tried a few sensor apps and everything seems to work fine. On top of the auto adjustment not being as good as Kitkat's, the inconsistency is really bothering me.
EDIT: I am on stock rom. I'm sure that CM12 would solve this problem if it's a Lollipop bug, but I can't be arsed with a custom rom a this time. Looking for a stock based solution, or at least an explanation for this strange behaviour.
Hey guys, now that I'm all caught up and on MM, I've found an issue that's really kind of annoying.
Not sure how many people use Lux Auto Brightness over the default, but I've personally become very used to having it. Now with MM, Lux's notification overlay (which would normally replace the standard brightness slider) shows up as it's own notification rather than as a replacement. Kind of annoying to see 2 brightness sliders especially when the default brightness doesn't work while Lux is enabled.
Has anyone else experienced this and found a fix? I'm assuming this is an MM issue and I do plan on rooting once I get more than a couple minutes to do so, I'm assuming Xposed could fix it although I'm not too experienced with this alternative.
Thanks for the help!
+1
I tried a lot with and without root, unfortunately to no avail. There is a Russian patch for S7 but I do not dare to try on S6.