Database Users

Screen goes dim after a while

Hi,
i have a problem with my three days old HD. Besides the fact it seems to be much slower than it should be, the problem is the screen goes dim after a while. I'm not talking about it going black after a while, like it's supposed to, but in normal working mode it just kinda becomes darker, kinda like notebook screen goes a little dim when you unplug it from power. When i turn it on, it looks ok, but after a while, mostly after it first time goes black due to inactivity, the screen looks dimmed, no matter what i do, and after a few minutes it returns to normal, without any apparent reason, kinda random. At first i thought it might be something in HDTweak, so i did the factory reset, but it's happening again. Any ideas?

Try disabling the light sensor. It is supposed to adjust the screen brightness automatically, depending on the external light conditions. You can disable it in 'Energy', under Start -> Settings.

Well, it sort of works. When i disable the light sensor, i get the screen for adjusting the light on battery and AC. When i adjust the slider for battery, the screen lights up and it's ok. But, the moment the device locks itself (via HDTweak setting, the only thing i adjusted in HDTweak, it dims, and when i unlock it, it's still dimmed. Then when i again go into light sensor setting and press on the slider, it lights up. I don't understand what's going on. Faulty device maybe?

Also try changing the settings in the advanced tab.
Adding a minute or reducing a minute here seems to kickstart the device - and the annoying screen dimming goes away.
r
Andrew

[Q] Nexus 7 Not booting (Flashes google screen (2-3sec) and then black screen)

Hi,
So my missus dropped her tablet (again) and this time she managed to smash the digitzer. So I went to replace it along with a new screen...
6 months later I get around to changing the parts. I reassemble and try to fire it up.
The Google logo flashes up and stay for about 2-3 sec and the disappears. Then nothing happens.
I tried plugging it in for 10 hrs and retried. No luck.
I can boot into the boot loader and the buttons work.
When I "power off" the device, suprise, it shuts down, on power up the logo flashes again and nothing.
Next I try "start" logo flash and nothing
When I tried Recovery the same again, then after about 60 sec it flashed the funny colored Nexus logo (very quick flash) then nothing again
When I select "Reboot Bootloader" it restarts the boot loader.
I'v been crawling the internet for hours now and have only found repeated attempts of loading the bootloader and trying recovery mode.
I did connect the tablet to the pc for a minute and could see a file structure but haven't been able to do that again.
Can someone please help.
Thanks
Matt

I'm beginning to think that the memory with the os has been lost, I might try unlocking the boatloader and refreshing the oem Rom. Any thoughts?
Sent from my LT22i using Tapatalk

So I unlocked the bootloader and flashed the newest stock rom to the tablet and still wont boot.
Same as before, Google flashes up and then black screen.

So, I figured it out. It was working the whole time, only the backlight went off after the Google logo disappeared. Its not the brightness sensor as its reading correctly in GPS status. It seams to be a software issue.
I've set the brightness to a fixed level and it is working OK, when I set it back to auto adjust it turns the backlight off again, when I shine a torch on the sensor I goes bright again.
Sent from my Nexus 7 using Tapatalk

matthewobrn said:
So, I figured it out. It was working the whole time, only the backlight went off after the Google logo disappeared. Its not the brightness sensor as its reading correctly in GPS status. It seams to be a software issue.
I've set the brightness to a fixed level and it is working OK, when I set it back to auto adjust it turns the backlight off again, when I shine a torch on the sensor I goes bright again.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I am having the same problem as you have described above. After changing the digitizer/ lcd, the tablet boots up and google logo shows up for few seconds and the screen goes blank. It goes into recovery fine. How did you fix it?

Turns out it's the lux sensor. Turn it on wait for the Google logo to disappear and grab a bright torch and hold it over the lux sensor it's right beside the camera the screen should go bright once it gets to the lock screen. If not use the torch to see what's on the display and once you've unlocked the tablet set the brightness to constantly on full instead of automatic brightness and this will override the lux sensor.
Sent from my Nexus 7 using Tapatalk

matthewobrn said:
Turns out it's the lux sensor. Turn it on wait for the Google logo to disappear and grab a bright torch and hold it over the lux sensor it's right beside the camera the screen should go bright once it gets to the lock screen. If not use the torch to see what's on the display and once you've unlocked the tablet set the brightness to constantly on full instead of automatic brightness and this will override the lux sensor.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Thank you so much. I followed your suggestions and now Nexus 7 is back up and running.
But I am afraid of rebooting it because I wasn't able to replicate your instructions once I had to reboot for system update. I had to flash factory image through fastboot and had to redo the initial setup and then the screen turned on welcome screen. So, it is hit and miss. Sometimes screen does turn on after few minutes of booting and sometimes it takes several hours for the screen to turn on.
I have my screen brightness setup to full. Will this override the lux sensor permanently or only until the next reboot? What is your experience with the tablet since you discovered this solution? Again, thank you so much for your help. I almost gave up on it and was ready to trash it.

Setting it to full with auto off should kick in after boot. When mine boots up it doesn't show the swirling dots but once it's done loading it pops up with the lock screen. I read somewhere that YouTube overrides the brightness setting and defaults back to using the lux sensor. I downloaded and paid for lux auto brightness that can override all app brightness settings permanently and it worked a charm for me. Maybe give to lite version a go and see how you get on.
Sent from my Nexus 7 using Tapatalk

matthewobrn said:
Setting it to full with auto off should kick in after boot. When mine boots up it doesn't show the swirling dots but once it's done loading it pops up with the lock screen. I read somewhere that YouTube overrides the brightness setting and defaults back to using the lux sensor. I downloaded and paid for lux auto brightness that can override all app brightness settings permanently and it worked a charm for me. Maybe give to lite version a go and see how you get on.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Thanks, just downloaded Lux Auto Brightness. Will see how it goes.

[Q] [BUG][LOLLIPOP] Screen "Flash" bug on screen timeout / manual lock

I'm having a couple issues with my nexus 4 after upgrading manually to Lollipop with the system image from Google Developers.
Sometimes, when the screen goes idle and turns off automatically or when it's turned off manually using the power button, the screen flashes on a higher brightness and shows the lockscreen before turning off. (I'm guessing the desired result is that the lockscreen should appear 'on screen' after the backlight is completely off).
What this causes is that when turning off the screen, the screen dims with the animation (fade to black and turn off), but before (and sometimes after) the animation is complete, it flashes for a few milliseconds displaying the lockscreen/background, even when locking the phone inside an app.
I could upload a video of the issue at a later time.
This bug didn't happen on any version/rom that went through my phone (many stock, many custom). Although I haven't tried installing another 5.0 ROM / AOSP.
The update also brought back a [hardware?] issue this Nexus 4 unit also has had since I got it. When dimming the screen using the brightness slider, sliding to the lowest setting turns off the backlight completely (effectively making the screen pitch black instead of dimming). This issue has been reported before and I was using Gravitybox to override the system lowest brightness level. Could these two issues be related? (Note that this issue didn't trigger this behavior before).
This issue has been reported by other users here:
http://forum.xda-developers.com/nexus-4/help/zero-brightness-t2168071
http://forum.xda-developers.com/nexus-4/help/problem-nexus-4-brightness-t2052857
https://www.youtube.com/watch?v=dvgt17sKQsU < this shows the screen going pitch black at lowest brightness, it happens either from the widget, the slider, and the option in settings.
Any ideas on why it happens or how can it be corrected?. Do you also have this issue?.
Many thanks in advance.

TWEAK/TIP - Prevent accidental unlocks

One of the big issues I have found, mainly with CM based ROMS, is that the option to prevent accidental unlocking seems to be missing/unavailable.
I've been testing various apps and utilities that monitor the proximity sensor, but there is one big issue - they monitor for screen on, but it seems in CM12.1 that the monitoring app doesn't work or get a screen on signal when you're using a lockscreen.
So the solution is not to check for screen on, but check for screen unlock.
I have a TASKER profile set up as follows:
If screen unlocked and proximity sensor on, then turn the screen off.
Works really simply. cover the proximity sensor with a bit of cloth or something and test it - if you double-tap the screen on, or it wakes due to a notification, the screen still goes on. But any subsequent action, eg slide to unlock or click on a notification, triggers the screen unlock flag, and this then checks to see if the proximity sensor is covered, and if it does, it turns the screen off again.
I CAN POST SCREENSHOTS IF ANYONE WANTS FURTHER INFO - BUT I'D SUGGEST GIVING TASKER A GO AND A PLAY ANYWAY, IT'S A BRILLIANT APP.

Lockscreen anomalies

I'm not sure if i'm posting this in the right place but couldn't find any other more appropriate location. I'm running Oxygen 9.0 build A6013_34_181001 and I've already noticed a few bugs.
I have my phone set to use fingerprint unlock and pattern unlock. Pattern lock is configured such that the pattern line is NOT displayed when I enter it. This works fine, except after a reboot. Upon rebooting the phone I'm prompted for my pattern unlock, and the pattern is displayed when I enter it. After this one instance, the pattern display is correct and consistent with my setting. Subsequent pattern inputs don't display the line, it's just the first one after boot.
I also noticed a strange issue with the fingerprint unlock. When the screen is off and I double tap to turn on the ambient display, normally I put my finger on the fingerprint sensor and the display brightness increases. I'm assuming this is to provide illumination for the fingerprint sensor to function and get a good image of the fingerprint. Sometimes when I put my finger over the sensor the screen doesn't brighten, and the sensor can't read my fingerprint. I know it's detecting my fingerprint and trying to read it since I get the animation on the display around the sensor, the screen just doesn't brighten and the sensor can't read my fingerprint.
There have also been some instances where the double tap on the screen doesn't turn the ambient display on. I can use the power button to wake the phone, and that works fine, but periodically the double tap just won't turn the ambient display on. I like this feature so I can quickly check if there are any pending notifications without having to press any buttons, most often when my phone is lying on my desk.
I haven't been on any of the OnePlus forums yet. Do they have a forum for bug submittals?