Database Info

Blank screen

Hey,
So last night my Sensation was on charge when I received an email. When I tried to unlock the phone the screen didn't activate but the lights for the buttons at the bottom did. I tried a few times but was unsuccessful, though luckily a hard reset seemingly fixed the problem.
Has anyone else had this issue? I've already contacted Orange and they said they'll replace the handset.
I recorded a quick (and pretty poor quality ) video on my old BlackBerry that I might try and put up on youtube later.

probobly the launcher is loading or force closed. im not sure though, it happened to me too

Happened to me once so far

Hm, probably something that will be fixed in a future update then?... Still, might get a new handset anyway - I may see some improvements in battery at least.

Screen Color Problems on Unlock (Really Weird)

I'm having a very strange problem with my Charge. It seems like pretty much every other time I unlock my phone, a color from the RGB spectrum is missing. Which in turn causes the screen to be a weird shade of blue, green or red. I can lock and unlock the phone again and it will be totally normal, but as I stated above, it seems like it's happening quite a lot more often here recently, and I'm wondering if anyone else has had this problem? I know I'm going to call Verizon tonight or tomorrow and see about getting a replacement because it's definitely not a software issue that I can see.

I had that happen once, and only once. However, it hasn't happened since then, so I'm pretty sure it was software related. Have you done a hard reset yet? If not, you need to do that to rule out a software issue. You need to try it for a bit in that clean state before loading 3rd party software to confirm.

I have the same problem, which just started this morning. When I woke up and looked at my phone, as it unlocked, sometimes it had a bluish or greenish tint. This would appear intermittently as I unlocked my phone.
I searched the internet, and found other instances of this happening as well.
I restarted my phone, and the problem hasn't returned since. Something to keep an eye on, but I'm hoping it's not hardware related, but rather software related (and can be fixed with a reboot).
Mko.

I had that happen a couple times. I have not seen it in a long time but it is software related. I could get it to do it a whole lot one day and after a reboot it never happened again.

I've never had this happen to me but I heard the Fascinate had a problem with the screen since amoled was still being developed, you can just attempt what these others have tried(factory reset, reboot, etc)
Sent from an awesome phone using an awesome app.

Homestar1217 said:
I'm having a very strange problem with my Charge. It seems like pretty much every other time I unlock my phone, a color from the RGB spectrum is missing. Which in turn causes the screen to be a weird shade of blue, green or red. I can lock and unlock the phone again and it will be totally normal, but as I stated above, it seems like it's happening quite a lot more often here recently, and I'm wondering if anyone else has had this problem? I know I'm going to call Verizon tonight or tomorrow and see about getting a replacement because it's definitely not a software issue that I can see.
Click to expand...
Click to collapse
For me when I unlock the phone it does a black screen with lines for a second,pretty much 5 out of 10 times I unlock my phone. I've already got a replacement charge,so my old one and the new one do it. I'm sending my phone to Samung because Verizon has sent me two charges with scatches on the screen, one also has a dead pixel.

Only had the weird color thing happen once upon unlocking several weeks ago. Locked and unlocked it again and it was normal again. Haven't had it happen again.
Sent from my GummyCharge using XDA App

I had this happen to me pretty consistently when. I tried running GummyCharged GBE. Rebooting didn't work for me, so I went back to GummyCharged FE, and that's what solved the problem for me, but it's possible that reflashing GBE may have done the trick too. I never tried that because I thought the issue was related to the ROM.
Sent from my SCH-I510 using XDA App

Well I called Verizon, and while they didn't have it listed as a known issue, I was told to reboot because it was more than likely a software issue. I did just that and haven't had this happen since.
Having said that, I noticed something else, the screen was at a different brightness nearly every time I unlocked it and it wasn't a funny color. Either full on 100% or dim as could be, never anywhere in between. I also stumbled upon an article from a lesser known tech site that suggested that the auto-brightness function was indeed the culprit. Seems to make perfect sense given what I saw. I've had this happen once in a blue moon before the other day, and as others stated after a lock/unlock all was well, but this was a different experience altogether. Hopefully this software problem can be fixed with an update (GB maybe? Probably right as they release Ice Cream Sandwich...).
As a side note my screen also does the gray lines once in a while, just 2 or 3 down the whole length of the screen for a split second before an unlock. Seems like it's not an issue so far.

I've had a completely black screen--my lockscreen will flash and just go black, but sliding where the normal unlock would be turns on the display to Home. Kind of odd, and I've only seen it twice.
Sent from my Droid Charge running GummyFroyo 1.9.1

Camera Not Starting or showing black

I was wondering if anyone else has experienced this problem. I am having an issue when I start the camera application it just shows the camera UI but the rest of the screen where the camera preview would be is totally black. On that screen hitting the buttons don't do anything.
If I open an application which uses the camera like Instagram it comes up with the error "Cannot connect to camera" or the screen goes totally black.
I am a bit of an Android noob but I can't figure out why this is happening. I have tried clearing the camera app's cache and force restarting it. It doesn't seem to help. The only way I can get the Camera to start working again is a reboot and then it might only work when I first boot it up. If I try again 15 minutes later it starting messing up again.
If you guys need any other info let me know, thanks for the help

return it, mine is just fine.

I tried to exchange it and all the AT&T stores are sold out
This is a pretty frustrating problem, compounded with the fact it seems I'm the only one having it.

Might be a dumb question but have you done a factory reset? Clearing cache normally will do the trick but if not, I'd go with a reset.

Well everyone, the camera problems turned out to be a symptom of a much larger problem that started happening. The LCD eventually started going rainbow whenever there was motion on the screen or I touched it. What this has to do with the camera I have no idea but I think there was something really wrong the hardware I got.
It's hard to explain what it looked like but it was like a seizure inducing flashing of white and other colors of the rainbow. Basically the LCD was failing or there was a loose connection in the hardware somewhere. I called AT&T and they were really awesome about it; they called all my local stores to find a One X for me so I could exchange it today. They even had the store set one aside for me, nice work AT&T.
When I got to the store all the employees gathered around to see my epically failing One X and everyone agreed the screen would kill a an epileptic person in short order. 10 minutes and I was out the door with my brand new HOX fresh out of the box. Overall this was not the experience I was hoping for my first few days with the phone but it was just my turn to get a dud I guess.
Couldn't be happier now that I have a fully functional phone, this thing is seriously amazing.

There are duds in every batch. Glad you were able to get it exchanged just fine

How to check if you have stealthy random reboots. Post results here.

My Z3 sometimes does "stealthy" auto reboots when not in use. The system crashes and does an auto reboot but not a full one because the phone won't ask for the sim pin code, it will reboot to the lockscreen so unless you're looking at the phone while it happens you won't notice. If you're lucky enough to catch the reboot, you'll notice the screen suddenly lighting up, and the boot animation will play, then the phone will go back to the lock screen where you left it. My phone does this a couple of times a week, most of the times I don't catch it but there's a way to tell: go to Settings → About Phone → Diagnostics → SYSTEM INCIDENTS
If it shows 0 this means you haven't had a reboot in the past 10 days. Right now on mine it shows 1 which happened during the night (so I didn't catch it happening). I always have 1 or 2 in there, I'm not sure if it always happened, but I started noticing it after Lollipop, and factory reset didn't help.
Please let me know if you have any "system incidents".

MarkMRL said:
My Z3 sometimes does "stealthy" auto reboots when not in use. The system crashes and does an auto reboot but not a full one because the phone won't ask for the sim pin code, it will reboot to the lockscreen so unless you're looking at the phone while it happens you won't notice. If you're lucky enough to catch the reboot, you'll notice the screen suddenly lighting up, and the boot animation will play, then the phone will go back to the lock screen where you left it. My phone does this a couple of times a week, most of the times I don't catch it but there's a way to tell: go to Settings → About Phone → Diagnostics → SYSTEM INCIDENTS
If it shows 0 this means you haven't had a reboot in the past 10 days. Right now on mine it shows 1 which happened during the night (so I didn't catch it happening). I always have 1 or 2 in there, I'm not sure if it always happened, but I started noticing it after Lollipop, and factory reset didn't help.
Please let me know if you have any "system incidents".
Click to expand...
Click to collapse
Hi Mark
I know this phenomenon on custom Roms or when using a custom kernel.
I think this is called a hot - reboot, kinda, because it's not a full reboot.
If you're using w custom kernel this might be the reason, or the settings of the kernel.
I can't check what you requested because I'm using the concept rom atm.
But I'm quite sure I don't have this issue, as I remember from kk days that the notifications are gone afterwards and I think this would go for lp too, and I didn't notice so far (on this rom).
But I did have had random reboots many times at different set ups of course. It can also occur on certain stock kernel settings or root apps I assume.
Gesendet von meinem D6603 mit Tapatalk

Aronuser said:
Hi Mark
I know this phenomenon on custom Roms or when using a custom kernel.
I think this is called a hot - reboot, kinda, because it's not a full reboot.
If you're using w custom kernel this might be the reason, or the settings of the kernel.
I can't check what you requested because I'm using the concept rom atm.
But I'm quite sure I don't have this issue, as I remember from kk days that the notifications are gone afterwards and I think this would go for lp too, and I didn't notice so far (on this rom).
But I did have had random reboots many times at different set ups of course. It can also occur on certain stock kernel settings or root apps I assume.
Gesendet von meinem D6603 mit Tapatalk
Click to expand...
Click to collapse
My phone is completely stock and I still have these weird reboots. Before I do another factory reset I'm trying to understand if other people have them (and then not bother with a factory reset because that would mean it's a firmware issue) or if I'm the only unlucky one who keeps getting them. Anyway, I was considering getting my phone serviced, I noticed the glass is a bit misaligned and I have a dead pixel, I called the service center and they said both issues are covered by the warranty. Might as well add random reboots to the list, maybe they'll get me a refurbished phone, mine has a few marks on it.

I factory reseted my phone and then sent it in for repairs, most likely got a refurb too since this one looks brand new, and I still have those "system incidents" happening early in the morning when the phone is just resting on my table.
I don't like begging for replies but please if you stumble upon this thread just drop a line saying if you have them or not. At this point I can't be the only one.
Also I'd like to know if there is any way to consult a log or something that would tell me why it happened.

I used to have them on kk, but they stopped. Mine would only happen at work, which led me to believe it was network related somehow... As if a spotty signal was heating up the phone or something. They stopped as randomly as they started.
Sent from my SM-T700 using XDA Premium HD app

I factory reseted my phone again after messing with the concept rom, and guess what, not even one day passes and the piece of crap reboots out of nowhere like always. I'm so mad right now, I only have 3 thirdparty apps installed, poweramp, the app from my mobile data provider and waze. I will start to try and get rid of this phone now, this is absolutely ridiculous.

I have exactly the same problem. Started after installing LP. Had someone found a solution?
Sam

Wait, is this happening on the Concept ROM? Because if so, you do know that's an unfinished ROM, right? Not meant to be a daily driver?
Clean flash the latest stock LP and go from there.

robogo1982 said:
Wait, is this happening on the Concept ROM? Because if so, you do know that's an unfinished ROM, right? Not meant to be a daily driver?
Clean flash the latest stock LP and go from there.
Click to expand...
Click to collapse
Dude, read the post again. It's happening on stock lollipop with literally no mods installed. I kept the concept rom for 5 days and it was absolutely stable for those 5 days. Stock lollipop reboots at least once every 10 days, but usually twice.
Here's a recap: I had the phone for quite a while now, I don't remember if I had reboots on KitKat, but I definitely have had them for the past 2 months or so. Meanwhile I got my phone refurbished because I had a dead pixel, it was already rebooting when I sent it in, got it back factory reseted and hardware refurbished and the reboots continued once I started installing all my stuff. Now I installed the concept rom to check it out, went back to stock lollipop with a full factory reset via PCC and after a day with pretty much nothing installed I had another reboot. The only thing that was kept during all this time is my 16Gb Class 3 SanDisk SD Card and my WIND (IT) nano sim card. I've decided to buy another SD Card anticipating the Android M memory unification feature, so I bought a Class 10 uhs3 32Gb SD Card from Kingston (which by the way isn't reaching anywhere near the declared speeds of 80/90mb/s, it only reads and writes at around 35 on the phone, I made a thread about it, maybe the phone itself can't read that fast), and I've been using it for a day now. I had no reboots yet but I had some weird app incidents under diagnostics, one from photo analyzer service and one from backup and restore (I hope they happened when I was still messing with the memory card in and out, because I didn't use any of those apps).
Here's a thread I made on the official forum:
https://talk.sonymobile.com/t5/Xper...oubleshoot/m-p/1057964/highlight/false#M26160
By the way, I still don't know if these reboots are rare or if everyone has them. Too few people have commented on whether they have them or not, while this thread has 447 views. If even 10 people commented saying if they had reboots or not I'd be able to rule out glitchy firmware. A friend of mine has the Z3C and he said he has no system incidents and his phone never rebooted.

Still getting soft/stealthy reboots
After doing a complete repair via pcc, I did not put a SD card back in my phone and only installed my google account and apps... No 3rd party apps. It goes for a couple days and then starts doing a reboot usually once every charge and mostly in the morning. The battery usage graph shows a pretty significant gap as if the phone was off but not completely off. Then I find system incidents in the diagnostic app but it only gives me the date and time of when it happens. No other information. Kind of useless if you ask me. This has all started after updating the official LP build . 200 firmware. Sony needs to investigate this became it's happening more and more for people on 5.1.1

I have a locked bootloader, stock kernel, rooted, xposed, dual recovery, tricked out rxz experience ROM with 85 apps (it includes 17-19 xposed add-ons) in addition to 102 system apps, no random reboots at all. I keep an eye on phone diagnostics, system status (temperatures, etc.) like a hawk.

So guys if this happens at you at stock rom , my suggestion is ask the service for replacement maybe.
Sent from my D6603 using Tapatalk

I am currently doing a test after repairing via pcc, installing a new Google acc, only important updates to apps I use that come pre-installed. So far it's been 5 days and no soft boots or incidents in diagnostics. Although it means nothing because usually after about a week or so is when the issues come back after doing a full repair or factory reset. I guess time will tell. Otherwise everything seems to be working great, especially battery life.

The blue light of death... No screen no safemode no boot

I've had my Samsung up and running for about a week now , did the two most recent updates . Today is the first time I experienced some serious problems . It started with a fingerprint scanner not working delivering an error message that read "fingerprint scanner has stopped working restart phone if this repeats" so after my second time of dealing with this there I restarted the phone . P at this point in time is when the blue light was lit up and has stayed lit up since I restarted it, this has been about an hour. I've tried every option on the recovery menu except factory restore. When I turn the phone on safe mode or not it goes straight to a black screen with the blue light continuously lit up . When I turn the phone off the light never turns off . I've tried hooking it up to the charger and doing all of the same steps above and still no luck. I have not installed any unknown apps other than ones on the play store and haven't had time to even explore rooting or ROMS yet. Seems to me like a brick by the stock software don't know if anybody else's experiences but I don't know what to do . Maybe someone can shed some light before I consider doing a factory restore , if that will even work.. I think this thing is bunked.
Edit~ I also tried pressing both volume buttons the power button and the home button all at once and it took me to a blue screen with the android logo and Galaxy written on the bottom . Nothing for a few seconds then it's says erasing and reboots....still a black screen and a solid blue light.

mattkilla420 said:
I've had my Samsung up and running for about a week now , did the two most recent updates . Today is the first time I experienced some serious problems . It started with a fingerprint scanner not working delivering an error message that read "fingerprint scanner has stopped working restart phone if this repeats" so after my second time of dealing with this there I restarted the phone . P at this point in time is when the blue light was lit up and has stayed lit up since I restarted it, this has been about an hour. I've tried every option on the recovery menu except factory restore. When I turn the phone on safe mode or not it goes straight to a black screen with the blue light continuously lit up . When I turn the phone off the light never turns off . I've tried hooking it up to the charger and doing all of the same steps above and still no luck. I have not installed any unknown apps other than ones on the play store and haven't had time to even explore rooting or ROMS yet. Seems to me like a brick by the stock software don't know if anybody else's experiences but I don't know what to do . Maybe someone can shed some light before I consider doing a factory restore , if that will even work.. I think this thing is bunked.
Edit~ I also tried pressing both volume buttons the power button and the home button all at once and it took me to a blue screen with the android logo and Galaxy written on the bottom . Nothing for a few seconds then it's says erasing and reboots....still a black screen and a solid blue light.
Click to expand...
Click to collapse
What firmware are you on? If you've taken the most recent updates, don't worry about rooting. Probably won't happen at least for a while. If you have a warranty, I would use it. If you get a new phone, don't take any updates if you might want to root.
If you want to keep this phone you should try the factory reset or the emergency recovery in SamsungSwitch.

Tulsadiver said:
What firmware are you on? If you've taken the most recent updates, don't worry about rooting. Probably won't happen at least for a while. If you have a warranty, I would use it. If you get a new phone, don't take any updates if you might want to root.
If you want to keep this phone you should try the factory reset or the emergency recovery in SamsungSwitch.
Click to expand...
Click to collapse
I'm not sure which firmware was on it, I did not pay attention before I took the update. I do know I have taken 2 updates in the last week since I received the phone.
I took the phone to a Verizon store and of course, seemed like going backwards. The rep tried all the same things I had tried and ended up calling a customer service rep to help him figure out what to do. Because the phone was purchased online my business' HR lady had to order another one online( which they replaced for free). Not sure what the problem ended up being but I know personally the most recent update BRICKED the phone.
New phone is up and running and thank you about the advice to not update if I prefer root. I love the stock ROM so I was really only going to root to de-bloat alot of the stock apps that are repetitive (i.e. messaging, messages, and Hangouts) .
So as of now no known fix to this blue light of death, except get a new one.

mattkilla420 said:
I'm not sure which firmware was on it, I did not pay attention before I took the update. I do know I have taken 2 updates in the last week since I received the phone.
I took the phone to a Verizon store and of course, seemed like going backwards. The rep tried all the same things I had tried and ended up calling a customer service rep to help him figure out what to do. Because the phone was purchased online my business' HR lady had to order another one online( which they replaced for free). Not sure what the problem ended up being but I know personally the most recent update BRICKED the phone.
New phone is up and running and thank you about the advice to not update if I prefer root. I love the stock ROM so I was really only going to root to de-bloat alot of the stock apps that are repetitive (i.e. messaging, messages, and Hangouts) .
So as of now no known fix to this blue light of death, except get a new one.
Click to expand...
Click to collapse
Check out your firmware in settings, about phone. If your build ends in OC3 or OE2, it can be rooted.
Glad you were able to get a new phone.

OC3!!???
Sent from my SM-G920V using Tapatalk

mattkilla420 said:
OC3!!
Sent from my SM-G920V using Tapatalk
Click to expand...
Click to collapse
Good for you! Pingpong is so easy you can be rooted in less than a minute.