There is a bug where of you reduce the brightness down as far as it will go, the screen is completely black.
This means its impossible to do anything, including increasing the brightness
The only solution is to reflash. Same with a replacement unit, so its a software problem.
Can I get a 3rd part ROM? It looks like this is the same tablet as an archos 80 cobalt.
Is there a utility in the play store that will fix the brightness so that my kids don't play with it again..
Related
Hi all
I've had my tf300 for a few days now, and I have a different kind of screen brightness problem. When watching movies or looking at pictures, they often look like they've been recorded/taken with very strong lighting like very strong sunlight. The effect isn't influenced by the brightness settings on the tablet, high or low the effect is still visible. The first tf300 I had did the same thing, so I returned it, figuring it was a problem with that particular tablet, but the second one does the same thing.
I've "solved" the issue by downloading screen adjuster from marketplace and setting the brightness setting in that app to 70% or less. Apparently that app adjusts a different screen brightness than the one the built in one does, because by using that screen brightness adjustment the effect disappears.
Anyway I was wondering how widespread this issue is - if it might be an actual defect or ASUS just screwing up the brightness settings of the screen.
Regards
I use a very dim display to save battery on the Surface or any other mobile device. The adaptive (auto) brightness feature isn't truly the best for the Surface for sure. I noticed that the screen flicks too much even though you're in the same environment. On reading about it on the web, I figured that this is a genuine problem for many on the tablet. Bad design maybe. So instead of reducing the brightness to minimum, I kept it at almost like 7-10% and voila ! The display is now as crisp as its supposed to be ! I wouldn't guarantee if it won't flick at all, but trust me, its like 90% better
Enjoy your new Surface !
screen flickering
Hi,
I've also noted some light flickering issues on my Surface (that I really like) even if the auto-brightness feature is off and with 100% level.
Generally speaking, it's not visible unless :
- you're scrolling quickly through the start screen
- you're closing an app with the proper gesture
It seems that for half second the scrim flickers...is it also happening to you ?
I was considering a RMA but I'm not sure if it's more a SW problem than a HW one.
Thank you for your answer.
Fabio
rustedfate said:
I use a very dim display to save battery on the Surface or any other mobile device. The adaptive (auto) brightness feature isn't truly the best for the Surface for sure. I noticed that the screen flicks too much even though you're in the same environment. On reading about it on the web, I figured that this is a genuine problem for many on the tablet. Bad design maybe. So instead of reducing the brightness to minimum, I kept it at almost like 7-10% and voila ! The display is now as crisp as its supposed to be ! I wouldn't guarantee if it won't flick at all, but trust me, its like 90% better
Enjoy your new Surface !
Click to expand...
Click to collapse
I think its more visible when you're on the Metro UI or the Start screen. And more on when I am scrolling from the side of the screen, just like you said. Its pretty weird.
Not sure if this is a Nexus5 or Android issue ...
Not sure if this is because I'm moving from an AMOLED to a IPS LCD ...
but I find the Auto-Brightness less of a function and more of a roller coaster ride.
- At home, in a well lit environment, the phone defaults to max brightness, which doesn't seem correct.
- In a dark room, upon wake of the phone, it correctly selects a lower brightness, yet will randomly ping up to max brightness, then settle back down.
The screen on the Nexus5 is absolutely gorgeous, but it just can't seem to select and lock onto the proper brightness level with respect to ambient light.
Is anyone else experiencing auto-brightness wonky-ness? Are there any potential fixes?
Everyone AFAIK suffers from it on nexus 5.
I have a horrible feeling it's a hardware fault, as none of the other Google devices on kitkat have this issue.
yeah the auto brightness seems to be too aggressive, but i'm sure custom roms will have the ability to tweak the auto brightness settings. i think even gravity box has some tweaks for the brightness
If you download Android Sensor Box, you can check the Light sensors. I think it may be bugged with Halogen lighting (correct me if I'm wrong). My home is ~ 18 years old, and we have some bulbs that have not been changed yet (yellow). Sometimes when I use my N5 under those lighting, the sensors go whack and don't register properly picking up 0lx, then spike up to 30000lx. Once I move to areas in the house with newer bulbs, the sensors work normal, picking up the right readings. I'm not sure if it's a rom issue or hardware issue, but my cousin also has a N5 and his worked fine. I tried flashing a new rom and mine still acted up fresh after boot (1st app installed after fresh flash was Android Sensor Box to test).
As a rule I don't use auto brightness. Just get something like lux or install exposed and enable a mod to let you adjust it by sliding your finger across the notification n shade. Easier and faster.
Sent from my Nexus 5 using Tapatalk
I find that autobrightness will auto-turn on, even when i don't want it to.
There is something funky about it, I can either make the phone too dark (using lux) or too bright (using default settings)
I'm still not happy.
Tried Lux, tried adjusting the brightness tables via Gravity Box, used Twilight (to dim at night), no matter what, N5 just wants to be at full brightness all the time!
I had my Nexus 5 in the cinema the other day. The phone was sat in the cup holder by the chair for the most part of an hour when I quickly replied to a text. On turning the screen on it was on full brightness and what's worst is it took around 10 seconds for it to go down. There is definitely something not quite right with it.
Aria807 said:
Sometimes when I use my N5 under those lighting, the sensors go whack and don't register properly picking up 0lx, then spike up to 30000lx. Once I move to areas in the house with newer bulbs, the sensors work normal, picking up the right readings.
Click to expand...
Click to collapse
Hi, I have been experiencing this as well, so I attempted to fix this at ROM level. The solution requires Xposed framework, so it works only on rooted devices (related discussion).
I have the auto brightness and with +5 on my Tab 3 8.0", but the screen is so dark i have to input brightness manually...
Is this supposed to be this way?
me too. hopefully we hear something soon
my 315 does it too.... I find that it just takes a bit of time for the light sensor to adjust. Sometimes, I tip the tab towards the nearest light and then it will 'auto' brightnen up, then it's good to go. Just have to wait it out, or go to manual when you have to.TIP.... when in manual... if you just want a little more brightness... dont 'slide' your finger... rather..'roll your finger' tip to the side.. You'll get finer adjustments that way..
good luck
My SGT3 10.1 is also like that. If the room is somewhat dark, so is the tab. But like mentioned above, if the room lightens up, so does the tab. LOL I don't believe there is an issue, just the nature of the beast. Because I think the tab is too dark I take auto brightness off and just leave it where I feel comfortable.
As with the others above, my T310 8" suffers from the auto brightness being way too dark therefore making it unusable, I'd hoped that the upgrade to KitKat would fix this, but it didn't, it's still useless.
I've tried a few 3rd party apps that can auto control the brightness and several of them work well, the easiest one to use seems to be YAAB (Yet Another Auto Brightness), it's stable and very quick to setup. The only downside I've found to this one is that the adjustable brightness slide function in video players (you slide your finger up and down on the left hand side of the screen) no longer works when YAAW is set to auto, but it is no big deal to turn YAAW off and make manual adjustments if you are going to watch lot's of video on the device.
*Sorry not to be able to give a direct link to the app on the playstore, I've not made enough posts to be allowed to do this yet
I don't know if anybody else here has suffered this, but I've read several times when googling, that many XZP devices came with input lag out of the box. My device has always suffered with this, and flashing custom ROMs didn't seem to make a difference.
Input lag means that sometimes, keystrokes/touches are completely missed and sometimes scrolling misses too.
I unlocked my bootloader really early on, so I never wanted to send it back as I'm sure this voids my warranty.
I tested for a faulty digitizer using various screen input test apps from playstore, and they usually don't show any areas of the screen as faulty. This has always made me believe that it was most probably a software issue.
Today I discovered that yes indeed, my issue is definitely a software issue.
THE FIX:
Changing the screen resolution to 4k (3840x2160), and DPI to 821.
I've tried this before but never noted the difference in touch input. Perhaps because I wasn't looking for it.
Today I tried it again and much to my surprise, this time I noticed a HUGE improvement to input sensitivity and for now has 100% alleviated the problem. Typing, tapping and scrolling works perfect now.
This is most likely caused by the screen having to rescale pixels from 1080p to 2160p, making extra work for the CPU, but I'm no expert so I might be wrong. But it works for me.
I'll also note that I'm using Turbo ROM p75B now, and the input delay was still there until changing the resolution.
I'd like it if somebody who has suffered the same issue could provide feedback, I really hope this helps you too, as this was the only real issue that have me buyers regret, and it now works wonderfully.
Cheers.
Edit: I do believe this topic might be better recognised in the guides and discussions category. If so, could a mod please move it there.
Luckily I haven't had this input lag issue. However, I do get input lag if I have stamina mode turned on, and set to battery time preferred.
Just so you know, you do know that you're only emulating 4k, right? The only way to set the display to 4k is on AOSP.
@iKlutz I can't seem to find the resolution settings lol
Yes I understand that it's only "emulating" 4k and that it's not native 4k. It also uses more battery, which would suggest higher CPU usage, which in part contradicts my theory about rescaling causing input lag.
Perhaps it is something to do with the "touch map" (I can't think of the term), the software/grid that maps out the touchable area to the digitizer, having to resize from 1080p to 2160p, making the grid inaccurate? But it wouldn't make sense as to why it only affects some devices.
Also, I do not have stamina mode enabled as it's almost pointless in today's phones. I believe limiting processing speed only makes process queus take longer to finish, which means that CPU takes longer to idle. It only saves a negligible amount of battery unless your phone screen is off for 80% of the day. Almost as pointless as closing applications and cleaning RAM, as your phone will just use more battery rebuilding caches and restarting processes.
In any case this has completely alleviated the issue for me, so I hope someone on Google ends up here and this may be a solution for them too.
gavster26 said:
@iKlutz I can't seem to find the resolution settings lol
Click to expand...
Click to collapse
There are some threads here that explain various methods to change the VM resolution and scaling. If you're unfamiliar with ADB, I suggest you read very carefully and take precautions, as setting the resolution wrong could make it really difficult to reverse the procedure and we currently don't have a way to make TWRP backups.
i noticed this too.. but i enabled glove mode and things sorted by it self..
this kinda works, it happens very much less frequently but it does still happen