I have an issue with my s6+, I have flashed several custom roms and the issue persists. This is my second s6+, and both this and the first were very bright the first few months. It seemed that something caused a dimming to occur, usually after I changed from stock (I used cf auto root without incident). The dimming is just enough that when I am outside in the sun, I am barely able to see the screen, and I can see the screen actually flicker to a dimmer setting, as if I have auto-brightness on. I do not, an even if I did I would think the opposite would occur. As of this moment I have TWRP installed and am running 6.0.1 marshmallow on Stock (Systemless Root). Any help would be really appreciated as I know you devs are busy and this is not the most high priority device. Thanks in advance!
Related
Hi Everyone!
So i got the OTA 2.3.4 upgrade for my TMobile G2 a couple of weeks ago and my keyboard backlight stopped working, I have seen many threads about this all over the internet (and very few actually here) but no one knows a solution to the issue yet. I was hoping someone can guide me here how to fix this. I know ultimate way to fix is to downgrade to Froyo.
I also have all the other issues that came with this "HTC screwed with" version of Android like constantly forceclosing with the dumb Tell HTC button, navigation icon disappearing when GPS chip is off, typing E sends me to short cuts, etc. The only real problem is the keyboard backlight because it has made the phone useless to me.
Thanks!
USA TMobile G2
Never Rooted.
OTA Upgrade to Android 2.3.4 with stupid Tell HTC app the only HTC footprint in the phone which is continuously freezinfg and forceclosing my apps.
Kernel 2.6.35.10-g96de068
Build Number 2.15.531.3 CL82286
Baseband 12.52.60.25U_26.08.04.30_M3
Without knowing too much about this particular issue (haven't heard of it personally) I'd say to do a factory reset, and/or dive into your auto backlight settings. The keyboard lights are tied to ambient light sensor.
Are you opposed to rooting? Sounds like you're having a lot of problems with your stock setup...
martonikaj said:
Without knowing too much about this particular issue (haven't heard of it personally) I'd say to do a factory reset, and/or dive into your auto backlight settings. The keyboard lights are tied to ambient light sensor.
Are you opposed to rooting? Sounds like you're having a lot of problems with your stock setup...
Click to expand...
Click to collapse
Actually the light sensor doesn't work either, I put the phone to my ear and my cheek starts dialing becuz the screen doesn't turn off, aft a minute it does automatically though. Then I pull the phone away from my face to hang up or dial an extenstion and the screen is off, I have to push the power button and slide to unlock.
I had rooted my old G1 and I had so many issues and speed problems that I figured I don't do that to this phone, it worked almost perfect with Froyo with a few issues but this one without keyboard backlit is 100% useless.
There is no setting in my setup for keyboard backlight or light sensor.
Well it definitely isn't a keyboard issue then, its a light sensor issue.
I'm not aware of any way to calibrate a light sensor etc. but maybe someone can add their input on that.
I know that if you are willing and able to root, you can flash a pre-rooted stock ROM or custom ROM and you won't have this problem.
I just found out when I change the screen brightness the keyboard light turns on, after I finish typing shut the keyboard and open again it doesn't turn on anymore. I can go back to home page tap the screen brightness on the widget and turn the keyboard light back on again.
Sorry to Bump! But please help! I tried rooting my phone but its just too many steps. I installed Android SDK which is hundreds of megabytes and was stuck there. Too difficult to use (I rooted my G1 many many times and installed various ROMs including CM7 so I am very familiar with rooting). I tried rebooting and erasing the phone to factory setting and still the same issue.
Hi,
I know I'm late to the party but I just picked up a BLU Life One cheap, which is basically the same phone as the Canvas 4 A210. So far I like the phone but the one thing driving me crazy is that after about 10 seconds the screen dims - whether auto-brightness is checked or not. I've found that it corresponds to the capacitive buttons (back, menu, home) turning off. It's surprising that there is no setting to keep the lights on or off.
I have rooted and installed Xposed Framework but have yet to find the module that can control this. Any suggestions?
Thanks,
Edit:
So I've discovered that the screen dimming issue is a BLU thing. After flashing a couple of the Micromax A210 roms, the screen dimming issue goes away. Unfortunately, my data speeds drop down to edge, as pointed out by cabegol. I tried flashing his modem fix, but to no avail. I will try again next weekend when I have more time to play with the phone.
Hello! Firstly I'd like to say thanks to any regular posters, this site helped me root my phone in the first place! I am trying to sort out what might be the cause of this problem and remove it, hopefully without starting over, as it was a pain in the butt to get the phone set up how I wanted and I do not have a full night to commit to it at the moment.
I have a Samsung S2 (the t-mobile branded one, sgh-t989), android 4.1.2 (kernel 3.0.31-1003885). This problem is recent and came on suddenly without changing any settings or installing any new software. The phone behaved normally for the first few months I owned it, it is a used phone, however, and I have no idea how the original owner treated it.
The problem is that brightness becomes tied to one or more of the sensors, and it takes several restarts, or sometimes days of waiting for the problem to go away. The brightness most often becomes tied to the accelerometer, where having the phone pointed at 45 degrees (or 01:30 o'clock), results in near 0% brightness, while returning to full brightness at 90-0 (or 3 through 12 o'clock). Occasionally it ties to another sensor (proximity?) or changes seemingly randomly, and once or twice has tied to the compass, with North being the brightness sink (with a similar 'darkness range' to orientation). The problem starts without a discernable cause.
Whatever the problem is, it also appears to disable, or for the most part inhibit multitouch. Around the time the problem started, tasker disabled and refuses to re-enable, if it is relevant. Shortly after the problem started, any push notification began turning on the screen (with a normal timeout, however). The problem persists through changing of any of the settings, toggling any modules, and through multiple resets, and never resolves itself without a cycle of multiple pulling-outs of the battery. After it is resolved, it usually remains fixed for a day or so before re-appearing.
If anyone has any suggestions for chasing down the problem, or has heard of anything similar, I'm all ears. I would like to avoid doing a factory reset, especially since I have no assurance it will resolve the problem. I'm happy to provide any additional information. Thanks for your help!
The first official LineageOS ROM was released for ocean last Friday, Sept. 12, and I am probably the first person in the world to install it to my brand-new XT1955-5
With the help of @roadkill42 and others, I flashed the ROM yesterday and everything was working fine.
Today we moved on to flashing Magisk and then Gapps. Yes, I know that is not usually the order of operations but we did it that way because we were having problems with TWRP, it was freezing the touch screen.
So, after we set up MagiskHide, we had to go back and flash Gapps, because we needed to install Termux from the play store to complete the MagiskHide Props Config setup.
Right after flashing Gapps, the display started acting up.
Any help appreciated.
If you go to settings->display->color and change it from normal to boosted or saturated it comes back. Pretty sure this is just a small bug.
I can't receive sms but I can send so give it some times for bugs to be fixed lol
Display problem as well
Jellypowered said:
If you go to settings->display->color and change it from normal to boosted or saturated it comes back. Pretty sure this is just a small bug.
I can't receive sms but I can send so give it some times for bugs to be fixed lol
Click to expand...
Click to collapse
Hello together,
I have exactly the same problem.
But I can't see a menu settings->display->color boosted etc. in German menu
My device is nearly unusable
Could you help, please?
Thank you!
The same sometimes with CrDroid 6.9
I have somtimes the same problem: colors in images wired blocks like wrong GIFs with only 32 colors, but the black&white text is normal e.g. Firefox text & images. Changing the display settings (for the germans: in CrDroid: Einstelltungen/Display/Farben) one ore two times, it changed to normal.
Menue color found already
lu10010 said:
I have somtimes the same problem: colors in images wired blocks like wrong GIFs with only 32 colors, but the black&white text is normal e.g. Firefox text & images. Changing the display settings (for the germans: in CrDroid: Einstelltungen/Display/Farben) one ore two times, it changed to normal.
Click to expand...
Click to collapse
Hi,
thank you, I found the related menu to set the color now
It seems to work!
KR
bitkrake
The settings change does remedy the issue temporarily, but it returns after a reboot. People are reporting this issue with LineageOS, and CrDroid, so you're not alone OP. It's related to Live Display. Resurrection Remix doesn't have this issue because they've removed Live Display from their ROM altogether, so it's worth giving that ROM a shot if you want to keep your device updated.
I think this problem happens after the root, Magisk.
Didn't happened with non rooted Lineage OS.
Just disable live display b done
so as long as the live display is not on then there are no issues.
I'm having this issue even with live display off, turning off live display is one of the first things I do during install and it's happened to me on all 3 of my installs thus far. It seems to only show up directly after I turn my screen on.
I'm using nitetime on aggressive doze mode, is anyone else having this problem using it as well?
I got the same problem with LOS18 (lineage-18.1-20210424-nightly-ocean-signed.zip) installed.
It appears only after rooting with Magsik.
Is there meanwhile any real and not temporarily solution for this?
Actually I think the problem has nothing to do with Magisk -- I am now also experiencing it without, and I seem to not be alone:
https://www.reddit.com/r/LineageOS/comments/mmwuli
https://www.reddit.com/r/LineageOS/comments/mmxvm7
Magisk just makes it a lot easier to reproduce the problem.
Unfortunately, I am using LineageOS for microG, so I think the Lineage devs will reject by bugreport. Can someone else report the bug at https://wiki.lineageos.org/how-to/bugreport ?
Hi all, I have the LE2127 T-Mobile version of the OP9 Pro, and recently I have been having a strange issue with it. I am using the stock firmware, locked bootloader, nothing significant changed on it, running OxygenOS 12 (LE2127_11_C.19).
Sometimes, when I wake the phone from sleep, one of two things will happen:
1. The fingerprint sensor will not light up properly, and will instead remain the same brightness as the rest of the screen and appear as a dull white circle.
2. The entire display will get set to maximum brightness, and remain that way until I reboot the phone.
Nothing really screams at me in logcat, and removing and re-enrolling the fingerprint doesn't seem to work either. I also have factory reset the phone, to no avail. The bug happens intermittently with no real way to reliably reproduce that I've found. The only way to get the screen back to normal and to make the fingerprint sensor work again is to reboot.
Any ideas?
My last time updating to the current A12 on TMO LE2127, I couldn't get the fingerprint sensor to work once I set it up in settings. I went back to 11.2.9.9. Fully rooted.
I'm too.
BCXB said:
Hi all, I have the LE2127 T-Mobile version of the OP9 Pro, and recently I have been having a strange issue with it. I am using the stock firmware, locked bootloader, nothing significant changed on it, running OxygenOS 12 (LE2127_11_C.19).
Sometimes, when I wake the phone from sleep, one of two things will happen:
1. The fingerprint sensor will not light up properly, and will instead remain the same brightness as the rest of the screen and appear as a dull white circle.
2. The entire display will get set to maximum brightness, and remain that way until I reboot the phone.
Nothing really screams at me in logcat, and removing and re-enrolling the fingerprint doesn't seem to work either. I also have factory reset the phone, to no avail. The bug happens intermittently with no real way to reliably reproduce that I've found. The only way to get the screen back to normal and to make the fingerprint sensor work again is to reboot.
Any ideas?
Click to expand...
Click to collapse
I'm too
No9p ✨ said:
I'm too.
I'm too
Click to expand...
Click to collapse
That's A12 for you, I suggest going back to 11.2.9.9 A11 and staying there for awhile. I hated A12. Latest is not always the greatest!
I've also been dealing with this issue. Talked to support and they said just to restart the phone when it happens. They are working on a fix