Don't know if anyone else is experiencing this with their Play but as of a week or two ago the backlight started acting strange. The backlight will randomly stay off when I push the power button with the slider gamepad closed. Only way to make it come on is to pop out the slider. It seems to be random, and if I push on the slider edge slightly with my thumb with the slider closed the backlight randomly flickers, ranging from slight to severe.
The display is still working despite the backlight issues, I can open apps, and use the phone normally but the backlight flickers on and off. Makes it especially hard to use the phone in the dark.
Phone has never been dropped once.
I've replicated this problem with a variety of roms, both custom and stock. It's definitely not app related or even custom kernel related. It happens on a fresh wipe with stock rom with stock kernel. It happens on CM7 with custom kernel.
I'm curious if anybody else is experiencing this. It would tell me if it's just an isolated incident or if others are having this problem.
Sounds like a faulty connection to the backlight to me.
I had the same problem 2 days ago. Then I couldn't get my phone screen on at all!
I sent my phone back to Sony, even thought I bought it second hand. Phoned them up and talked to them. They asked what time of year I bought it so I said around August and then they gave me the address to send it to. Now I'm just waiting to see what happens next.
If your going to send your phone to Sony for repair then make sure you put the fresh firmware back on and un-root your phone as that breaks the warranty (unless they don't know about it)
Hope I helped you. If I did then click the thanks button
Sounds like a faulty ribbon cable to me. (cable that connects the screen to the rest of the phone)
You wouldn't need to drop it for that to go bad, It could just be a case of opening and closing the gamepad or lot.
Yeah good thoughts, most likely the ribbon. That really sucks because I've only had the phone for 7 months, and I've taken excellent care of it. Sounds like a major design oversight.
Mine is probably near complete failure at this point. It's taking a lot more effort to keep the screen on now. Fearing soon it won't work at all.
In hopes that this might help someone else down the line, I was able to fix my problem. Yesterday the screen pretty much quit and I had no choice but to try and solve it myself or buy a new phone.
Using this disassembly video as a visual aid I carefully pulled my phone apart: http://www.youtube.com/watch?v=-3n5ZfkqhzE
You'll need a torx T5 tool to pull out all the screws but they are cheap.
Underneath the phone and jammed into the screen ribbon was a rather thick hair just hanging out. Somehow it buried itself in there. I removed it, unplugged and replugged the screen ribbon and cleaned the dusty inside with a q-tip and reassembled it all together.
It works fine now, so hopefully this helps someone else avoid having to pony up for a new phone. For those under warranty probably best to send back but for those like me with no warranty it's worth the shot.
Good morning to all ..
I want to ask if anyone of you has the same problem: when I leave the galaxy nexus in charge in the night (all night) in the morning, when the alarm rings, I can not turn off the alarm because I can not use the phone, because I can not unlock the phone, if I touch the ring in the lock screen, nothing happens, as if the touch screen does not work but if i wait a while(15-30-60 seconds) it will wake up and i can re-use my phone.. and this problem has also occurred at other times... without the phone was in charge..in the afternoon, I could not answer a call arriving(not often).. let me say this thing that perhaps can be decisive, that my cell was 2 times under warranty, the first replacement for faulty screen (ehm...) and the second time because when they replaced the display does not have removed blue film that protects the far side of the screen next the front camera(i get i blue overlay effect on front camera images lol)..than i send it in warranty again.
it may be caused by the rom/kernel? if not, how you recommend to act?
ps: I was wondering also .. if when they replaced the display have replaced only the AMOLED part or also the glass and the multi-touch ... because the glass was intact and the multitouch worked.. is a single body or are separate pieces? Also remember that the phone stank of "liquid crystal" because they were leaked (this was the fault of the display, it was broken..) it might have caused the malfunction of the touch sporadically?
from what ive read sometimes rom's can screw up functions like camera etc, but if there tried and tested not sure why it would be a prob.
i would go down the warranty route personally.
big_mike_aka_mike said:
from what ive read sometimes rom's can screw up functions like camera etc, but if there tried and tested not sure why it would be a prob.
i would go down the warranty route personally.
Click to expand...
Click to collapse
mmmmmmmh...is the last resort .. I would avoid because they put us a month to fix it! this is the third time i would send it in the warranty .... almost makes me want to let them replace it with another device ... I fear them have ruined ...
what is your min mhz set to?
I had a similar problem with my old cappy running CM9. I had to restore it via Odin and start from scratch then it worked and didn't have that issue again. My suggestion would be to go back to 100% stock and then customize it again. It may or may not help but it is worth a shot.
sent from my GSM Galaxy Nexus
I just sent mine into Samsung for repair, due to the same thing happening. It started off that if I pulled the battery I could get it to work, but eventually it got to the point where that woudln't even work. Between this happening and the fact that I returned another one due to the out going audio dropping, I am starting to loose faith in the GNex.
Zepius said:
what is your min mhz set to?
Click to expand...
Click to collapse
i use 384Mhz (franco kernel first frequengy step) minimium frequency @ ondemand governover...isn't it the stock minimium frequency?
@thephoneguyusa i have tried... but i got the same thing with all stock, flashing factory images got from http://code.google.com/intl/it-IT/android/nexus/images.html ( i don't remember if i've rooted and changed the kernel, but i'm 99% sure that was all stock,maybe i'll give a try, again )
@HitchHiker my gnex crashed once (a good fall) and the display is ****ed .. but the glass and touch were intact ... is very sensitive .. but this is not good ... if I send, this will be the third time that I send it in for service since I bought it in December ... no good...
curiosity: attached the blue-film-front-camera-rendering-blue-effect-lol...
UPDATE:
I didn't use the charger last night and this morning I had the problem in question. But! I went to the bathroom to shower and the various routines gnex morning bringing with me, and I left the bathroom I wanted to use the phone, but! tataaaaan! the screen won't unlock...can humidity cause this problem?
my room is a bit wet because I live near the sea ...
perhaps too much humidity **** circuits of the touch .. or perhaps it is a contributing cause to a real defect of the display....
Hello all!
I have noticed that recently, my phone has been doing a very odd thing while charging. When it has been plugged in for a little while, and the screen is on and in use, sometimes the phone will crash. When it crashes in this manner, the backlight on the screen is turned on on full brightness, the screen gets a yellowish hue, and horizontal black bars start appearing on the screen. More black bars keep appearing until I reset the phone (hold the power button), and then there is no evidence of any screen problems. I also generally have to unplug it for a while, as if this happens once, it generally happens multiple times until I unplug the phone and wait. These problems seem to be occurring at odd times (a lot at night, before I am going to sleep), and have just started happening (I also recently made the upgrade from the latest version of GB to 4.0.4). I have had this device for about a year now (the second device, the first one had a physical design flaw and was replaced), and I am out of warranty right now, so any help would be appreciated!
a_p3rson said:
Hello all!
I have noticed that recently, my phone has been doing a very odd thing while charging. When it has been plugged in for a little while, and the screen is on and in use, sometimes the phone will crash. When it crashes in this manner, the backlight on the screen is turned on on full brightness, the screen gets a yellowish hue, and horizontal black bars start appearing on the screen. More black bars keep appearing until I reset the phone (hold the power button), and then there is no evidence of any screen problems. I also generally have to unplug it for a while, as if this happens once, it generally happens multiple times until I unplug the phone and wait. These problems seem to be occurring at odd times (a lot at night, before I am going to sleep), and have just started happening (I also recently made the upgrade from the latest version of GB to 4.0.4). I have had this device for about a year now (the second device, the first one had a physical design flaw and was replaced), and I am out of warranty right now, so any help would be appreciated!
Click to expand...
Click to collapse
That was happening to me (for a weird reason, my devicewas new, its seems that problem is more common in the rogers version dont know why) but, if your problem is the same problem that i had, then, just install stock ICS with oneclick (dont remember the name very well)
lorddavid said:
That was happening to me (for a weird reason, my devicewas new, its seems that problem is more common in the rogers version dont know why) but, if your problem is the same problem that i had, then, just install stock ICS with oneclick (dont remember the name very well)
Click to expand...
Click to collapse
Superoneclick? That's the closest I found, and it doesn't say that it supports the Glide. And, I am running a fully stock version of 4.0.4, unrooted and everything. I might need a little more help here, haha.
I mean, oneclick, is the firmware,and is about 700 mb, give me amoment a will search it
EDit: i found it: http://www.androidauthority.com/captivate-glide-sgh-i927-att-android-4-0-4-ics-uclg9-leak-110365/
I use that, when I install it, that problem gone away, try it. And then, you can flash the custom recovery and install custom roms
lorddavid said:
I mean, oneclick, is the firmware,and is about 700 mb, give me amoment a will search it
EDit: i found it: http://www.androidauthority.com/captivate-glide-sgh-i927-att-android-4-0-4-ics-uclg9-leak-110365/
I use that, when I install it, that problem gone away, try it. And then, you can flash the custom recovery and install custom roms
Click to expand...
Click to collapse
Isn't that a different version though? The build number on that is UCLG9, not UCKJ3 (which is what I have right now).
I am not sure, but, if with that your problem persist, maybe is hardware, but I only do that. When I did it, that was the latest version, now there is another version but not sure what is it
I was having the same problem, except it was happening frequently after my phone had warmed up due to normal use. If the phone was already hot it wouldn't even get past the splash screen.
I put it down to hardware fault, and was successful in getting it replaced under warranty. The new one has been totally fine.
Hopefully yours isn't a hardware issue - but from how it sounds it very well could be
davidpartay said:
I was having the same problem, except it was happening frequently after my phone had warmed up due to normal use. If the phone was already hot it wouldn't even get past the splash screen.
I put it down to hardware fault, and was successful in getting it replaced under warranty. The new one has been totally fine.
Hopefully yours isn't a hardware issue - but from how it sounds it very well could be
Click to expand...
Click to collapse
I really was hoping it was a OS issue, as it hadn't ever done this on GB. If I flash a new rom then, it would be fixed?
Also, I too noticed that my phone is abnormally warm when it does this. I do have a cover on my phone, but I noticed that it seems to be centered about on the horizontal center of the phone, about a half-inch below the camera. If this is related, what do you think it is?
My phone did this as well. Luckily it happened just before I rooted. The att guys said it was a hardware fault and that fault also killed my battery. I'm assuming it was a short. It started as something infrequent, but it eventually escalated to the point the second I turned it on my screen turned completely green and got really hot.
Exxon02 said:
My phone did this as well. Luckily it happened just before I rooted. The att guys said it was a hardware fault and that fault also killed my battery. I'm assuming it was a short. It started as something infrequent, but it eventually escalated to the point the second I turned it on my screen turned completely green and got really hot.
Click to expand...
Click to collapse
Just great, a possible hardware problem while out of warranty. Did yours do it only when charging as well?
a_p3rson said:
Just great, a possible hardware problem while out of warranty. Did yours do it only when charging as well?
Click to expand...
Click to collapse
Didn't have to be charging to do it. Could have been on the street holding it. (I was on GB as well)
Exxon02 said:
Didn't have to be charging to do it. Could have been on the street holding it. (I was on GB as well)
Click to expand...
Click to collapse
Your issue sounds similar, but slightly different. Mine only happens while I am charging it, and it has only done it since a while after I made the upgrade to 4.0.4. Although, they sound similar, and my phone also gets concerningly warm, so I have no idea if it is the same thing or not...
If it's out of warranty, then you have nothing to lose by doing a backup and a clean ROM installation, which is what I would do. I guess if you do it when fully charged and while the phone is cold you should be fairly safe, especially if you use a small ROM. I've found the latest M3 10.1 ROM installs fairly quickly, so that might be worth a shot even just to see if it fixes the problem.
The only risk you're taking is that the phone might die and get bricked in the process if it's a hardware fault, so I guess it's really your call.
EDIT: On that thought, perhaps experiment with seeing if you can charge after leaving it in the fridge for about 15 minutes? It's a trick we used to use to recover data from failing hard drives, if you get them cold enough they can work for long enough to get away with things
davidpartay said:
On that thought, perhaps experiment with seeing if you can charge after leaving it in the fridge for about 15 minutes? It's a trick we used to use to recover data from failing hard drives, if you get them cold enough they can work for long enough to get away with things
Click to expand...
Click to collapse
I like that idea, as it should fix the overheating issue. However, the times that it actually has this malady aren't regular - it seems to happen more at night, but not every night. I could try putting it in the freezer when it does it though, and see if it works. If it is overheating, could it be a hardware issue then? I also noticed that my battery that I have in my phone does appear to have a slight dent near the bottom, and it is only happening when it is charging, so I am wondering if it could be a problem with the battery? When I pull the battery out after it has done this, the battery itself isn't that warm, but the phone is, so I'm thinking it isn't the battery, but does anyone else have any ideas?
Ok, so i'll start of by saying rougly 6 months ago I bought an unlocked T999V with a flashed ROM which was liquidsmooth 4.3 I believe. The phone worked perfectly fine up until a week ago. The phone was dropped off a desk and landed on its screen, nothing was broken so I thought nothing of it. The night afterwards I noticed a few darkish spots when I would look at the phone at night, only if the background was dark though (setting menu for example). The phone was plugged in when I went to turn it on and it wouldn't. Its unresponsive and I am unable to put it into DL or recovery mode. Leading me to believe its hard bricked and will need a jtag fix. But WHY? Why did dropping my phone all of a sudden mess up my screen as well as brick my phone ? Someone please help me out here :crying::crying:
yoimbeast said:
Ok, so i'll start of by saying rougly 6 months ago I bought an unlocked T999V with a flashed ROM which was liquidsmooth 4.3 I believe. The phone worked perfectly fine up until a week ago. The phone was dropped off a desk and landed on its screen, nothing was broken so I thought nothing of it. The night afterwards I noticed a few darkish spots when I would look at the phone at night, only if the background was dark though (setting menu for example). The phone was plugged in when I went to turn it on and it wouldn't. Its unresponsive and I am unable to put it into DL or recovery mode. Leading me to believe its hard bricked and will need a jtag fix. But WHY? Why did dropping my phone all of a sudden mess up my screen as well as brick my phone ? Someone please help me out here :crying::crying:
Click to expand...
Click to collapse
Are you comfortable opening the device? There's a chance the fall didn't necessarily damage anything, but knocked very important cables loose. I would check every cable connection on the motherboard, and check the battery prongs, as they may not be making good contact causing dead battery. Are you getting absolutely no response from the pc when connected?
Anyway, point is, checking the connections is the easiest thing to do- and you might be able to determine if anything else is loose (ie did it land on the power button and now it's stuck? Etc) It's likely something simple- so check that first, then you can move on to other diagnostics.
The Fall damaged Digitizer. Hence the dark spots. As to unresponsiveness, remove battery and then try. If it still does not work then Power button might be stuck or has loose wires.
I don't know I thought dark spots in a dark room on a dark background were norm for this type of screen- I have them too on a brand new led assembly. Google suggests that's normal and not necessarily damage, although it could be if they're appearing under normal lighting conditions. I agree with everything else though
Wonder if s/he got it worked out?
absinthesummer said:
I don't know I thought dark spots in a dark room on a dark background were norm for this type of screen- I have them too on a brand new led assembly. Google suggests that's normal and not necessarily damage, although it could be if they're appearing under normal lighting conditions. I agree with everything else though
Wonder if s/he got it worked out?
Click to expand...
Click to collapse
I brought it into a repair shop and was told the EMMC(?) chip was most likely bad and the phone needed a reflow. I put it in my oven and tried the reflow but no luck, I ended up buying a new T999 as I was quite happy with my first one.
Glad you now have a working device
If you dont care to reply, dont read. except moderator ofcourse.
tl;dr- screen black. not overheat .. touch works. even after black fading to complete black..d855... no paper/eraser/microwave stupidity..
Before you say its a common thing and is a repeat topic, let me tell you right away, its not..
Description-- D855.
phone screen goes off, more like fades away like some screwed up crt(i can see it going black from the sides and then slowly the whole screen)
when it happens -- anytime. at any moment.
what all i tried-- none. i find the paper logic stupid. i believe that if its such a bad processor, i might as well throw it away and buy anew one. i dont think its cpu problem..
why i think its not a cpu problem-- bcoz my touchscreen works perfectly even when device is fading. in fact at times when i lock and unlock again, all gets back to normal. no temperature related behaviours. it can happen even in a freezer. when it doesnt light up(the screen), phone still remains usable. i infact unlock the device with swipe up and go on home screen and i know where music icon is, and i click and then play cyanogenmod music player ((so use its viper4android even if screen is screwed).
no one mentioned whether during black screen the touch and all were working or not. mine is... so i feel its either the screen unit or the wire that connects it.
woyld really appreciate a proper answer if anyone could help me with this. i mean the word 'proper'/.. if any extra details needed, let me know, i will update. i just wanna pinpoint the thing thats causing the issue so that i can get part replaced if not super expensive. thanks.
PS- my battery has red indicator. like real bad since 3 months or something after it got in contact with water/. no device damage though. last time when it turned red, phone simply used to reboot randomly bcoz of low power for device to consume, but never used to look like some CRT screen slowly fading to black from sides crap.. so yeah.. thanks again
i think its the battery