It is quite bright, especially at night. Is there a way to control its brightness?
My Xperia 1 III is rooted if that's needed.
Thank you.
I just put the phone screen facing down
This is a technical forum and expects technical response to the asked question.
That's weird. My xqbc62-v notification LED is dim and has a narrow viewing angle. I can only see it at night.
I think there are multiple hardware revisions of this phone. My first phone was purple and crashed constantly. I returned it and bought a new one later. It's purple, but so dark that it looks back except under direct sun.
I see what you mean now. The BC62 notification LED used to track ambient light and it was always relatively dim. Starting with the Android 12 update, it's max brightness all the time. It's annoying at night.
Yep I can confirm that the LED is much brighter after A12 update. I charge the phone wirelessly at night beside my bed so putting it face-down is not an option. ;-)
What I have found to work is completely unscientific but works every time for me. I use a cable so not sure if it will do the same for wireless. After I plug it in I too notice that the LED is too bright. So I wait a minute or more and unlock the phone with my fingerprint (while the charging cable is still plugged in) and then double tap the screen to relock the phone. I use Nova Prime as my launcher which allows me to double tap to lock. Usually doing this makes the LED dim down considerably. Sometimes I have to do it 2 or 3 times but it always ends up working. YMMV
Anyone knowing a 2ay to disable the LED while charging? Maybe via adb command?
Related
Picked up a Thunderbolt and tonight while making a call at night I noticed the alert LED glows dim red and kinda flickers whenever I'm on a call. Can anyone verify that this is normal behaviour or do I have a defective phone?
The only thing that changes color is my notification bar. Is your phone plugged in?
no, not plugged in- i first noticed it while taking a walk. on second look it's a dim, somewhat flickery orange.
yeah i see that too. maybe thats the proximity sensor? idk.
I went to the Verizon store and Best Buy also and looked at the demo models- all 3 appeared to behave the same as mine with the faint orange/red LED on while on a call, so I'm guessing that's normal behavior. The salesman thought it was the screen that was lighting up the LED, but I turned off the screen and you could still see the LED was on.
Running the newest UnNamed and I'm trying to find a way to keep the screen on while charging from USB. The point is to keep the screen on while driving. At night I charge with AC power so that's not an issue.
I found posts saying there was a burn in problem with SMOLED screens being on with a static image for more than a couple minutes at a time. I haven't seen it personally but if anyone has first hand experience with this phone or the international model, please speak up before I damage my phone.
Otherwise, once again, it looks like I need Tasker for the job. Have it detect bluetooth connection for the car and upon usb power trigger car mode and keep the screen on at ~50% brightness. something like that.
With unnamed go to Settings>Applications>Development and click Stay Awake.
Try this first,
Menu->settings->Applications ->Development -> Stay awak
If not working , try this
Menu->settings->Display->Screen Timeout ->Never
Now I've never seen permanent burn in on my SGSII or Nexus One (even while on constantly during a 10h drive to Vegas). I was using a stop watch app on my Nexus One, and while only on for 5 minutes or so, I did see it burn in, but it went away after a few minutes of being off (boy was I scared when I first saw it though).
Now, I have personally seen permanent burn-in on a Vibrant (not mine).
Funny thing is the screen timeout is set to like 5 seconds on it, so it's barely on. Yet I can clearly see the clock is burned into the screen.
Have you tried running a car app to hold a screen lock? I know Google Maps can do that. Plus it doesn't require going into settings (at least more than once).
EDIT: As a simple observation, the burn-in seems worse when it's white on a black background.
Hi. 2-3 days before I did a Jelly Bean 4.1.1 update to my S3 from kies. (My country has DLJ1 release of JB). After the update i noticed some LED problem. When plugged my phone to plug, i noticed that my LED's Brightness has decreased (the red one, while plugged in). I plug out and plug in lots of times and only few of them shows bright LED. Also these bright LEDs loose it brightness again in 1-2 mins.
I tried the LED on notifications also. The same problem occurs again. Most of times the brightness is low from its usual.
Firstly i though it was a hardware problem and open test of my s3 from *#0*# and test my LEDs lots of time. In "EVERY" of the test, the LEDs are bright as sun and bright as usual before. So i start thinking that is a software/firmware problem.
Note: I also read a comment in another forum, someone also complain about this issue on "Charging Battery problem on JB.
So is this problem is usual and known or what. Do you know the reason and solution. How can i fix it? Thank you for your replies...
This is surely a widespread problem, I've found it too. As soon as I flashed official JB, I noticed the LED wasn't as bright. I suppose it's not a serious problem, but it isn't right.
Hi,
Happens the same here, with DLIJ4 ROM.
[]'s
Only affects the red charging notification and is a feature, not a problem. Less glare.
You make it sound like the end of the world... how sad.
Firstly i though like that but: If it is a feature why i can see very bright red LED while charging sometimes. As I said before, 90% times the brightness is low. However also as i said before in few times I saw bright red LED after a moment its gone again. If it is feature, is it normal ?
Also this happens in blue (notification) LED sometimes..
So i dont think as it is feature...
Not seen it on other colours, red is always dimmer than it was on ICS. I recall seeing somewhere that it was deliberate...
This is a feture. The LED brightness is now regulated automatically, depending on surrounding light.
I also tried in very dark room and also tried in under the lamp. But brigthness of LED is not change anyway I dont understand this ...
It seems that the surrounding light level is checked only when the charger is plugged-in and then in rather long interval.
I have the AT&T H900 V10 and I can't figure out how to keep the second screen from dimming when the main screen is off. It's so dim that I can't see it unless it's directory in front of my face, and no buttons seem to brighten it without during the main screen on. Is this something that can be changed? I'm not worried about battery life since it stays plugged in 99% of the time.
Same
Sent from my LG-H900 using Tapatalk
So far there doesnt seem to be any way to control this, other than covering the light sensor until the second screen goes off, then letting it come back on at greater brightness for 3 seconds or so until it dims again. Maybe LG is trying to make sure it doesn't drain battery but maybe they will adjust it with updates or give us control over it.
It pretty much makes the second screen useless as I can't see any notification without turning on the main screen.... and no LED light so this kind of makes me want to rage.
Hi all,
Since Android Wear 2.0 the dock mode while charging with clock doesn't work any longer. When placing Moto on the dock it shows a black screen. When touching the screen de clock appears for a moment and vanishes after about 1.5 seconds. It appears to be a bug. Do you all have this bug or is it just me. Did anyone tried a reset of the watch? I would really like to able to fix it , cause I use that feature a lot.
Same here.
A temporary solution I have found is to enable in developer options 'stay awake while charging' now it stays on. But it is not the same. The display appears to be much brighter. probably because ambient mode (Not sure that's how its called) is not enabled.
Edit: That appears to be the fix. When turning on in settings 'always on display' it works like before. no need to enable stay awake while charging in developers settings.
Although this fixes the issue, I am somewhat disappointed because this option reduces battery life.
I noticed I should have put this question into 'troubleshoot and questions'. I am sorry for placing it here. Perhaps a moderator can place it in the right section for me?
Not a problem here.
Always on is normally activated.
Sent from my m1 note using Tapatalk
I've noticed the same behavior when I upgraded my Moto 360 to AW 2.0
For me, the clock stays on but the background is really bright whereas it used to be black before
Same thing here, background to bright. I don't think this is on purpose. They would probably get out fixed in an upcoming patch(?)
Same here.
I liked docking my watch on my bathroom counter and using it as my clock while getting ready in morning. Now it doesn't stay on and when I tap the screen I can see it for a few seconds. When it is on ....the brightness of the background is terrible.
I sure hope they fix this problem.
I have the same problem
Can't believe there is still no fix for this?
This is really annoying! I was hoping XDA had found an answer. Having always on screen on is not a solution since Moto made a bad design decision on the screen making it best to turn that option off. I assume everyone else's keep awake while charging option doesn't really solve it either because the screen turns off once the battery is full. Anyone think there's a workaround to be found in Tasker and maybe AutoInput (maybe turn always on screen on while charging, off otherwise, or even based on hours). I'm no tasker expert, so I'm not sure if that combo could work on android wear.
Sn0w0nS said:
Hi all,
Since Android Wear 2.0 the dock mode while charging with clock doesn't work any longer. When placing Moto on the dock it shows a black screen. When touching the screen de clock appears for a moment and vanishes after about 1.5 seconds. It appears to be a bug. Do you all have this bug or is it just me. Did anyone tried a reset of the watch? I would really like to able to fix it , cause I use that feature a lot.
Click to expand...
Click to collapse
I have found this to be an issue when I use a charger that is not the Motorola plug that came with the watch. If you switch to the Motorola OEM charger you'll see a lag of about one to two seconds but the clock will always come on.
sebastianraven said:
I have found this to be an issue when I use a charger that is not the Motorola plug that came with the watch. If you switch to the Motorola OEM charger you'll see a lag of about one to two seconds but the clock will always come on.
Click to expand...
Click to collapse
Not on mine. I'm using the factory charger.
vladfan said:
Not on mine. I'm using the factory charger.
Click to expand...
Click to collapse
That's so odd. I'm not having that problem at all
sebastianraven said:
I have found this to be an issue when I use a charger that is not the Motorola plug that came with the watch. If you switch to the Motorola OEM charger you'll see a lag of about one to two seconds but the clock will always come on.
Click to expand...
Click to collapse
I am using Motorola's dock charger. I am positive that the issue lies with Android Wear 2.0 and not the charger. Before wear 2.0 it worked as it should.
I think it's random with AW2.
After flashing a new rom at my mobile, I had to forget and pair again the watch to the Android wear.
From now on, the clock stays on during charging.
This was not the case before that.
Sent from my m1 note using Tapatalk
I have the very same issue (watch paired with a Nexus 4, 5.1.1). Anything I can try? Thanks!
Well, at least this is validation for me. It's been driving me insane, and I'm almost positive it's killing my battery life. I used to be able to stretch a full week on a single charge, but now it's more like a full day.
I'm sure this is what everyone else has been experiencing: there is now a setting called "Always on screen" in Android wear settings. The new behavior for this setting is a strict enforcement of this property; that is, to be either always on or auto off. This seems absurd because before Android wear 2 (not sure if the option existed or not), it seemed to work as we expected, to auto off in active wear but stay lit while docked. There should at the very least be another mode for when docked/standby vs active wear.
Something else that makes it seem buggy is that when the always on screen option is disabled, and the watch is docked and charging, the screen is still faintly lit although only a blank black and no clock. I do think this is a bug and not a feature. For anyone interested, there are also settings for other things you might not be using. I'm turning them off and pray the battery gets better.
wesswei said:
Well, at least this is validation for me. It's been driving me insane, and I'm almost positive it's killing my battery life. I used to be able to stretch a full week on a single charge, but now it's more like a full day.
I'm sure this is what everyone else has been experiencing: there is now a setting called "Always on screen" in Android wear settings. The new behavior for this setting is a strict enforcement of this property; that is, to be either always on or auto off. This seems absurd because before Android wear 2 (not sure if the option existed or not), it seemed to work as we expected, to auto off in active wear but stay lit while docked. There should at the very least be another mode for when docked/standby vs active wear.
Something else that makes it seem buggy is that when the always on screen option is disabled, and the watch is docked and charging, the screen is still faintly lit although only a blank black and no clock. I do think this is a bug and not a feature. For anyone interested, there are also settings for other things you might not be using. I'm turning them off and pray the battery gets better.
Click to expand...
Click to collapse
What r u talking about?
Always On was there since Android Wear 1.5.
And come again?
1 week use of the watch with 1 charge?
How did u manage to do that?
By turning on the watch for 2 hours every day?
Sent from my m1 note using Tapatalk