Related
Would it be bad to keep my phone screen on for long periods of time? For example if I wanted to use it as a clock next to my bed. Would it have any impact on the screen if it was on all night? I have the HTC Surround.
i think it probably would, the image may burn into the display and remain there
is there a way to leave the screen on all night? I thought there was no way to disable the auto off feature, just a way to change how long it takes to turn off.
i don't think so. it will not harm your screen. no digit will never stay the same for more than a couple of hours. As the previous post says, there may not be a way to keep it on anyway.
I've had a lot of phones that keep the screen on when the phone is plugged in. So that may mean all night...and no screen burn has ever happened. If you can get it stay on, you'll be fine
Krissrock said:
i don't think so. it will not harm your screen. no digit will never stay the same for more than a couple of hours. As the previous post says, there may not be a way to keep it on anyway.
I've had a lot of phones that keep the screen on when the phone is plugged in. So that may mean all night...and no screen burn has ever happened. If you can get it stay on, you'll be fine
Click to expand...
Click to collapse
Unless you are using AM/PM clock format - M stays at the same place.
On the side note, I know AMOLED's are susceptible to burn-in, but I thought LCD tech had advanced to eliminate screen burn-in issues.
Never had a problem with LCD's - phone screen was left on every night on my TP2 whilst charging for the past 15 months with no ill-effect. Same on my Sony Ericsson C905.
Hi all
Just got my new unlocked One X today, but already I have problems with the software, Back, Home and Apps buttons lights going out out.
They seem to come on and off when ever holding the handset at a strange angle or position. Is this normal or is there a setting that needs to be changed to stop this from happening, or more likely the handset has a fault.
vlad_drac said:
Hi all
Just got my new unlocked One X today, but already I have problems with the software, Back, Home and Apps buttons lights going out out.
They seem to come on and off when ever holding the handset at a strange angle or position. Is this normal or is there a setting that needs to be changed to stop this from happening, or more likely the handset has a fault.
Click to expand...
Click to collapse
I am not sure about this but I never noticed this while on 1.26. Someone "complained" about it and I noticed this on 1.28. The 3 button led light only come on at night. So they are now sensitive to ambient light. Try to cover the front top part and you will see them come on. Remove your hands the led's go off.
But as said, I am not sure if it was like this when I was on 1.26. Didn't take any notice of that.
vlad_drac said:
Hi all
Just got my new unlocked One X today, but already I have problems with the software, Back, Home and Apps buttons lights going out out.
They seem to come on and off when ever holding the handset at a strange angle or position. Is this normal or is there a setting that needs to be changed to stop this from happening, or more likely the handset has a fault.
Click to expand...
Click to collapse
Haha... buttons illuminate at low light/night time conditions, no fault.
u can adjust the sensitivity with a rooted device but that is another story for another day.
Wow, I feel so thick.
I was so close to packing up the handset and sending it back because I thought it was faulty.
Cheers for the help.
vlad_drac said:
Wow, I feel so thick.
I was so close to packing up the handset and sending it back because I thought it was faulty.
Cheers for the help.
Click to expand...
Click to collapse
I was thinking the same thing. They are defo run on light sensor but it is too aggressive. If there is a small lamp on in a normal size bedroom they go out yet the light is no where near enough bright enough to see the buttons with out their lights on. Its making me have to send the phone back. Oh well SIII here I come..Pity! :-(
Soo close...
vlad_drac said:
Wow, I feel so thick.
I was so close to packing up the handset and sending it back because I thought it was faulty.
Cheers for the help.
Click to expand...
Click to collapse
Haha... I was just looking for the same issu...and was too soo close to repacking it for return... Glad I didnt :laugh:
---------- Post added at 11:46 AM ---------- Previous post was at 11:41 AM ----------
nickhuk said:
Haha... buttons illuminate at low light/night time conditions, no fault.
u can adjust the sensitivity with a rooted device but that is another story for another day.
Click to expand...
Click to collapse
Im ready for that story :laugh:
I have just had similar problem except my light stayed on, if I held it, the software buttons would flicker on and off and if I tilted it backwards would dim, even stayed on when phone was turned off. HTC tech said that it was faulty and the phone is being replaced.
nickhuk said:
Haha... buttons illuminate at low light/night time conditions, no fault.
u can adjust the sensitivity with a rooted device but that is another story for another day.
Click to expand...
Click to collapse
I´m also ready for that story!
Does anyone know how that works. I would prefer that they always stay enlighted, when screen is turned on. I´m using Viper X maybe that can help...
Kwagga65 said:
Im ready for that story :laugh:
Click to expand...
Click to collapse
For Venom-ROM I found it searching the Tweaks. Go to "Button" and set "Capacitive Backlight" to "Never " and they´re always on, when your screen is on. There are some 9 differeint steps to control the sensitivity.
Greetings
Segge
Here's a weird issue. I got my case, and it always succeeds in turning off the screen when I close it, but when I open it, there will sometimes be up to a 10 or 15 second delay before it turns on. Anyone else with a magnetic case seen this on the new Nexus 7?
It seems unlikely this is any kind of problem with the magnet. The case I got is this one:
http://www.amazon.com/gp/product/B00E5G39DK/ref=oh_details_o02_s00_i00?ie=UTF8&psc=1
(not because it is a really great case, but because it was available early and is better than nothing - the biggest problem is that it won't fold flat, though perhaps if the spine gets worked enough it will get better).
I got this exact case for my fiancee's N7.2, for the same reason as you (availability), and it works perfectly closing and opening the flap/lid. It wakes and shuts off the screen practically instantly.
EDIT:
Actually, I take that back, it's not the exact same case, but it is an i-Blason case: http://www.amazon.com/gp/product/B00E4WSGOM/ref=oh_details_o01_s00_i00?ie=UTF8&psc=1
Just happened to get this exact case and tried duplicating your issue and it is working flawlessly so far. Don't know what's up with your case or tablet
Well, it doesn't happen very much, but I've seen it a couple of times. It is definitely odd, but not a really big problem.
Do you open the case flat, or bend it back under?
Sent from my Nexus 7 using xda app-developers app
rmm200 said:
Do you open the case flat, or bend it back under?
Click to expand...
Click to collapse
This case doesn't really want to bend back all the way, but I do remember the first time I saw it happen I folded it back as far as it would go (about 20 degree angle) and put it on my desk, then about 10 seconds later the screen suddenly came on. I just wanted to clean the screen, so I was actually happy it didn't come on that time when I opened it, but then as I was reaching for it with the alcohol wipe, it turned on (maybe it is like a dog and didn't want a B A T H .
Claghorn said:
This case doesn't really want to bend back all the way, but I do remember the first time I saw it happen I folded it back as far as it would go (about 20 degree angle) and put it on my desk, then about 10 seconds later the screen suddenly came on. I just wanted to clean the screen, so I was actually happy it didn't come on that time when I opened it, but then as I was reaching for it with the alcohol wipe, it turned on (maybe it is like a dog and didn't want a B A T H .
Click to expand...
Click to collapse
Do keep in mind that the magnet will work from both sides of the Nexus. Folding the case back will act like the case is closed, only weaker.
Might come on, might not. Might turn off, might not.
A new bit of info (which makes absolutely no sense).
The delay appears to be correlated with having no wifi connection (I can't imagine why). If I have wifi, the screen always seems to come on right away. If I don't have wifi, then I (sometimes) get the strange delay. Even if I turn wifi off completely (which you would think would take it out of the equation), I still see the delay.
Claghorn said:
A new bit of info (which makes absolutely no sense).
The delay appears to be correlated with having no wifi connection (I can't imagine why). If I have wifi, the screen always seems to come on right away. If I don't have wifi, then I (sometimes) get the strange delay. Even if I turn wifi off completely (which you would think would take it out of the equation), I still see the delay.
Click to expand...
Click to collapse
When you wake the tablet, any apps you have running in the background that need to update information online will attempt to access Wi-Fi. This is mostly true for widgets that present information such as weather, blogs, news, etc., or update device status for things such as time, mail alerts, device statistics, et al. Some of these apps/widgets can be tenacious in their efforts to connect and might try pulsing several times to get a signal.
The apps/widgets that seem to be the most aggressive with ensuring that Wi-Fi is always available are the ones that infuse ads in some fashion. Some of these will refuse to run altogether. I have the Amazon App store on my devices but try to shy away from relying on it too much because most apps from Amazon will not run unless they can be verified online each time they are opened; even if the native app, itself, wouldn't require this.
One thing you may want to try is removing your widgets and try waking the tablet with Wi-Fi is turned off and see if the situation changes. If that doesn't work, then check if any apps are always running in the tray and if those could be the culprit. Another possible issue could be if you're running a shell or launcher as some of these try to refresh each time the device is awakened. Some of these shells/launchers aren't optimally coded and need to do a lot of recompiling and re-sizing on the fly.
Hope you find the culprit and can go back to enjoying your device without the hiccup.
I have same issue. I reset my Nexus 7 2 to factory setting. Problem resolved.
i have the exact same issue, i am using another case which comes with a magnet for auto screen on/off. sometimes it takes 5 - 10 seconds for my screen to turn on. it's quite annoying actually. does the old N7 have this issue??
---------- Post added at 12:05 AM ---------- Previous post was at 12:03 AM ----------
Mightym83 said:
Just happened to get this exact case and tried duplicating your issue and it is working flawlessly so far. Don't know what's up with your case or tablet
Click to expand...
Click to collapse
i have a different case and i have this problem too. it has soemthing to do with the tablet not the case
RedDevils88 said:
i have the exact same issue, i am using another case which comes with a magnet for auto screen on/off. sometimes it takes 5 - 10 seconds for my screen to turn on. it's quite annoying actually. does the old N7 have this issue??
---------- Post added at 12:05 AM ---------- Previous post was at 12:03 AM ----------
i have a different case and i have this problem too. it has soemthing to do with the tablet not the case
Click to expand...
Click to collapse
Have you tried backing up and doing a factory image restore? Also don't associate your google account initially so no software downloads.
I have a similar casee (Roocase Origami) with magnets, and I have the same issue. It works again if I manually turn the N7 on and off. But after a few tries it happens again. I think it's a Nexus 7 issue, not a case issue.
RedDevils88 said:
i have the exact same issue, i am using another case which comes with a magnet for auto screen on/off. sometimes it takes 5 - 10 seconds for my screen to turn on. it's quite annoying actually. does the old N7 have this issue??
---------- Post added at 12:05 AM ---------- Previous post was at 12:03 AM ----------
i have a different case and i have this problem too. it has something to do with the tablet not the case
Click to expand...
Click to collapse
I have a Poetic Slimline case with the same issue - unreliable magnetic on/off. I have Poetic Slimbook and Caseology Folio cases that work perfectly.
So is it the Nexus FHD or the case?
It seems like the Nexus since we all have the issue with the same different cases. Especially since the Nexus clearly knows the magnet is being removed; it just takes a while to turn on the screen. If you manually turn the screen on and off, then open and close the cover, the case works fine. But if you leave it alone for a minute, the issue comes back.
Nope, I do not wanna go through all the trouble just to solve this issue and without any guarantee on solving it too. I still can live with it but sometimes it's kinda annoying
Sent from my Nexus 7 using xda app-developers app
I have noticed that if I am switching between multiple public wifi access points sometimes it will become slower to respond or not respond to magnet at all.
This never happened at home where there is only onebap.
Someone mentioned on another thread wifi status affected their magnet on also.
Not saying this is definite, but maybe worth investigating.
I have issues when WiFi is turned on but not connected to a network. When it is on and connected or off it seems to work fine, however. Strange problem.
Hi. I am not sure this is the BSOD problem that others have had.
I bought a second hand i747. It came with 4.3. It will work fine for a few minutes when first turned on, then the screen will go dark. The menu and back buttons stay lit, and the touchscreen still works, the LCD just cuts off.
If I hit the power button, it sleeps the phone. When I hit again, the screen will come on, but only for about 5 seconds, then it's black again. Everything works, just black screen.
Is it possible for it to overheat or something? It doesn't feel hot at all, but if I turn it off and leave it for awhile, it will again work for about 2-3 minutes, then only about 5 seconds at a time again.
I swapped batteries, and it's the same. The battery had pink on it. I opened it up, and none of the other stickers showed water exposure, and the board itself was clean.
It has stock 4.3, and is not rooted.
I did go to phone settings and turned off the "darken screen during calls" checkbox.
I am wondering if the proximity sensor heats up and shuts the screen off. Grasping at straws I suppose.
Any idea of how to fix this?
Thanks
Perhaps a bad capacitor in the digitizer/lcd assembly? My TV had an issue with a bad capacitor that would cause the screen to blank out after a few minutes???
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I'll try swapping boards in it later, and maybe at least narrow down if it's the board or the screen assembly. I have an extra proximity sensor I could swap, but it doesn't seem like it's that to me.
thanks, will post more after the board swap
Update: I switched boards (different carriers), and I could not replicate the problem in either phone. I had hoped that would show that either the board or the LCD assembly was bad, but I didn't learn anything useful either way.
I put the boards back in their respective bodies. It still happens now, but not as often. It also appears to be totally random. I did switch batteries in the problem phone, and it doesn't seem as bad. I will try another battery switch and see if that helps it more.
When the screen goes dark, the menu and back buttons are lit. When it went out last night, I could see that there was still some faint background light that I can't see in the day. I pulled up Youtube and did a video, and when the screen went dark, I could still see movement, but couldn't make anything out. So, the phone is still going in the background.
If I push the power button, it sleeps, then push it again, and it wakes up just fine. Sometimes I have to do that 4 or 5 times for the screen to stay on. Sometimes it goes dark after 10 minutes of use, sometimes a half hour, sometimes just a few.
Any help is appreciated.
Well, right before throwing the phone into the wall, I noticed a partially removed liquid exposure indicator. I pulled the phone apart to check the motherboard.
In the process of taking it apart, I forgot to take out the SD card. In so doing, it pulled the sim/sd card module off the motherboard. Low and behold, there was a very light corrosive glaze in a few spots under the module.
So, I got out the 99% IPA, and a toothbrush, and cleaned the whole entire board. Since then, it seems to be working fine.
I don't know exactly what part getting cleaned fixed it, because I just cleaned the whole board.
Anyways, maybe that'll help someone with inexplicable issues downstream.
Thanks for following up with how you fixed the problem. In retrospect, water damage makes sense.
I dropped a Captivate into an ice chest full of melted water last year. I immediately pulled it out and the phone was mostly okay for a while but then the microphone didn't seem to work so well and occasionally the right third of the screen wouldn't respond to touch until I cycled the screen on and off. The water damage sticker and phone interior showed no signs of water.
I will probably sell the old captivate but with full diclosure about the history. Would have been nice if the seller had done the same for you.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Thanks, I should have thought of it sooner, but it didn't seem to have any signs of water damage otherwise.
I ordered the 99% IPA online, because I couldn't find any locally. It works wonders with previously wet boards. You might be able to bring it back.
Has anyone noticed any burn-in problems yet? I've seen reports of the problem for some other watches (LG), but so far nothing specific here for the Huawei.
It's so far so good for me, but I've been extremely nervous about this issue. I avoid faces with things like thick tic marks or logos in ambient mode. I know about Wear's built-in "protection," but I don't have a lot of confidence in it. Am I being unreasonable?
improvius said:
Has anyone noticed any burn-in problems yet? I've seen reports of the problem for some other watches (LG), but so far nothing specific here for the Huawei.
It's so far so good for me, but I've been extremely nervous about this issue. I avoid faces with things like thick tic marks or logos in ambient mode. I know about Wear's built-in "protection," but I don't have a lot of confidence in it. Am I being unreasonable?
Click to expand...
Click to collapse
I had the GWR and didn't have any issues with that at all. That said I turn the screen off at night during charging so maybe that helps. I'll keep an eye on the Huawei, but I'm hopeful that it will be fine.
dunjamon said:
I had the GWR and didn't have any issues with that at all. That said I turn the screen off at night during charging so maybe that helps. I'll keep an eye on the Huawei, but I'm hopeful that it will be fine.
Click to expand...
Click to collapse
I had the GWR for almost a year too. Always used watchfaces that are 'always on' (so no dimmed mode without background) and always had the charging animation on by night. Never experienced any burn-in.
I just powered mine on for the first time last night. I played with it for a few hours, then put it in the charger for the night and this morning it has burn-in!! How could it happen so fast??
mszach said:
I just powered mine on for the first time last night. I played with it for a few hours, then put it in the charger for the night and this morning it has burn-in!! How could it happen so fast??
Click to expand...
Click to collapse
Whoa! What got burned in? The little charging icon?
improvius said:
Whoa! What got burned in? The little charging icon?
Click to expand...
Click to collapse
The outline of the watch face. If I change the watchface and swipe left, you can see the outline of the other face as the background instead of white.
mszach said:
The outline of the watch face. If I change the watchface and swipe left, you can see the outline of the other face as the background instead of white.
Click to expand...
Click to collapse
hell no, wtf!!
it is very bad, sorry for that, were you using this watchface long time ago? what is the watch face look like in ambient mode? maybe the watch got really hot, and screen on while charging. i started to worry about the screen quality of this watch.
Edit:
i have seen this is your first day, i think maybe a faulty screen
Yeah, I'm wondering if your watch just froze in full display mode overnight.
mszach said:
The outline of the watch face. If I change the watchface and swipe left, you can see the outline of the other face as the background instead of white.
Click to expand...
Click to collapse
That deserves an RMA and you deserve a new replacement watch.
I sometimes get lag on mine, im not sure if it's actual lag or whether im doing something wrong but as someone mentioned if the watch went full brightness and is charging then the heat might have done it?
I returned it yesterday to best buy. Lucky me though. . they had cyber Monday deals and it was on sale for $50 less! !
I noticed that when the minute hands on mine move (ie every minute) that the whole screen kind of does a refresh. I'm using a custom watch face called InstaWeather, and in the settings there's an option to help with screen burn. I wonder if this is it? So every minute, every pixel would have been off/on or on/off?
dieselboy said:
I noticed that when the minute hands on mine move (ie every minute) that the whole screen kind of does a refresh. I'm using a custom watch face called InstaWeather, and in the settings there's an option to help with screen burn. I wonder if this is it? So every minute, every pixel would have been off/on or on/off?
Click to expand...
Click to collapse
yes, this is an android wear burn in protection buy moving a few pixels in all directions, works very good if you don't have large objects in the ambient mode, and won't help much if you have.
improvius said:
Has anyone noticed any burn-in problems yet? I've seen reports of the problem for some other watches (LG), but so far nothing specific here for the Huawei.
It's so far so good for me, but I've been extremely nervous about this issue. I avoid faces with things like thick tic marks or logos in ambient mode. I know about Wear's built-in "protection," but I don't have a lot of confidence in it. Am I being unreasonable?
Click to expand...
Click to collapse
In my opinion, yes, you are being overly worried. First the technologies itself has improved and we see less burn-in even when we set screens on to test such a thing. Second, the ability to move(write) a watch face or screen is not some huge leap, in fact it's really super easy to add to an OS to simply move the screen pin outs when in any long display mode. Beyond all that, app makers, watch face builders, now have the old data and make sure they write to avoid any long same display visual mode.
Easy to add to an app, when write same display, write 2 pixels, change.
Then after all that we have face on mode and ambient mode, which in my daily use changes my watch face enough that I would never get burn in. Agree that I am a heavy user of the watch, I tend to have to change twice a day. Perhaps someone that used the watch much less would have more of a concern?
I have the same problem
http://cl.ly/183c0O2m0m2q/amoled_vypaleny.jpg
Huawei Watch - after four days of use.
dj.kure said:
I have the same problem
http://cl.ly/183c0O2m0m2q/amoled_vypaleny.jpg
Huawei Watch - after four days of use.
Click to expand...
Click to collapse
****. What kind of messed up face watch/app did u use?
rusty.gh said:
In my opinion, yes, you are being overly worried. First the technologies itself has improved and we see less burn-in even when we set screens on to test such a thing. Second, the ability to move(write) a watch face or screen is not some huge leap, in fact it's really super easy to add to an OS to simply move the screen pin outs when in any long display mode. Beyond all that, app makers, watch face builders, now have the old data and make sure they write to avoid any long same display visual mode.
Easy to add to an app, when write same display, write 2 pixels, change.
Then after all that we have face on mode and ambient mode, which in my daily use changes my watch face enough that I would never get burn in. Agree that I am a heavy user of the watch, I tend to have to change twice a day. Perhaps someone that used the watch much less would have more of a concern?
Click to expand...
Click to collapse
Wrong. You must not understand what screen burn in is. No new technology has come out that will stop screen burn in. The software that moves the pixels over only works if the object is 1 pixel wide other wise it doesn't work screen burn in will still happen. And they do not have it where the same pixels won't be used otherwise in ambient mode it would jump around not wiggle.
dj.kure said:
I have the same problem
http://cl.ly/183c0O2m0m2q/amoled_vypaleny.jpg
Huawei Watch - after four days of use.
Click to expand...
Click to collapse
Reset the watch. It may not be burn in. I saw a bug like this from using too high Def of an image on a watch face. It got stuck in the cache even after I changed watch faces. I reset the watch and haven't had any issues since
Lepa79 said:
****. What kind of messed up face watch/app did u use?
Click to expand...
Click to collapse
Default watchface "Explorer".
---------- Post added at 11:08 AM ---------- Previous post was at 11:06 AM ----------
ShrekOpher said:
Reset the watch. It may not be burn in. I saw a bug like this from using too high Def of an image on a watch face. It got stuck in the cache even after I changed watch faces. I reset the watch and haven't had any issues since
Click to expand...
Click to collapse
Do you mean "Factory reset"? I did it, but nothing has changed.
ac16313 said:
Wrong. You must not understand what screen burn in is. No new technology has come out that will stop screen burn in. The software that moves the pixels over only works if the object is 1 pixel wide other wise it doesn't work screen burn in will still happen. And they do not have it where the same pixels won't be used otherwise in ambient mode it would jump around not wiggle.
Click to expand...
Click to collapse
Fare enough, just my opinion, & you have yours. Too bad you had to start by saying wrong.
Samsung has made changes to light output and color to reduce burn in, and we all know there is some type of display movement now to also reduce burn in, so it's odd you claim there has been nothing.
Anywho, I don't get burn in so yea, maybe with your attitude if you do, you deserve it?
rusty.gh said:
Fare enough, just my opinion, & you have yours. Too bad you had to start by saying wrong.
Samsung has made changes to light output and color to reduce burn in, and we all know there is some type of display movement now to also reduce burn in, so it's odd you claim there has been nothing.
Anywho, I don't get burn in so yea, maybe with your attitude if you do, you deserve it?
Click to expand...
Click to collapse
I'm not going to start it by saying you're right, am I? Samsung didn't make changes to anything in light output the only thing that's changed is adaptive screen color which is meant to adapt the screen contrast to show what's on screen in the best possible colors. There is no new technology that will stop burn in. You must not have understood me. The image wiggle is a software attempt to stop screen burn in from happening but it won't stop it just slow it down. Screen burn in will continue to be a thing until the panels we use change technology. I didn't say that nothing has been made to prevent it.
And if you sense attitude in a straightforward response that's on you. I'll let karma deal with that comment. I personally don't get screen burn in and I've had a SAMOLED device since the Samsung Epic. I just understand how to prevent it. But just because I've never had it I won't tell people that they're overly concerned about screen burn in.