Develop Bugs

Nexus screenshot issue

Hey everyone, I've been having a little bug that I noticed after I received the 4.0.4 update. I don't know what I exactly do to cause this but my nexus takes random screenshots whenever I press my power button to unlock my phone. I have the pattern lock that I use and when I hit power it randomly vibrates and when I go check my gallery it shows that I just took a screenshot. At times, when my battery is low it seems to randomly vibrate again and take a screen shot and gives me the prompt screen for which app I'd like to use to complete the action... No, I don't press the volume down key when this happens and no I don't have any screenshot apps. I'm stock, non rooted... Anyone else have this issue?

Stuck volume key?

adrynalyne said:
Stuck volume key?
Click to expand...
Click to collapse
I'm having doubts that it would be that...sometimes it does it even when I don't touch the power off key..

I have this same problem. I decided to find out what was going on when it asks what app to use, so I selected google drive. It uploaded the screenshot and a bug report to google drive. The bug report is a 3mb text file. I can't upload it here.

Same here with 4.0.4 IMM76I rooted,bootloader unlocked
Sent from my Galaxy Nexus using XDA

Do any of you guys run a rom that gives the ability to use the volume rocker to take screenshots? Have you tried reflashing your roms since you updated?
Sent from my Galaxy Nexus using Tapatalk 2

xterrain15 said:
I have this same problem. I decided to find out what was going on when it asks what app to use, so I selected google drive. It uploaded the screenshot and a bug report to google drive. The bug report is a 3mb text file. I can't upload it here.
Click to expand...
Click to collapse
Upload it somewhere and update your post with the link.
sent from my i9250

Posting the bug report
docs.google.com/open?id=0BxAJdhmCAyirSDU2UEU5dTRyQzg
There it is.
I am about to try flashing the 4.0.4 update again, as I just downloaded the zip of it.

Screenshots are Volume Down + Power. Bug Reports with screenshots are Both Volume Keys + Power. Do you have a case on? I've seen many people having these issues that were due to a tight fitting case.

Case
I do have a case on, but I know that's not the issue, as the power button is not covered, and this often occurs without me being anywhere near the power button. It can happen in the middle of typing out a text message. A prompt appears asking what application I'd like to complete this action with, and if I check the gallery later, there will be a new screenshot of my messaging app.

Slightly tangential - but is there any ROM or setting that will allow you to use a softkey to take screenshots? Or do I need to just search out an app that'll do so?
I find it really awkward (at least with my case on) to take screenshots and wouldn't mind the ability to do it with a softkey instead.

ceribaen said:
Slightly tangential - but is there any ROM or setting that will allow you to use a softkey to take screenshots? Or do I need to just search out an app that'll do so?
I find it really awkward (at least with my case on) to take screenshots and wouldn't mind the ability to do it with a softkey instead.
Click to expand...
Click to collapse
AOKP allows you to set up any functions/icons to softkeys
Sent from my Galaxy Nexus using xda premium

nirco68 said:
Same here with 4.0.4 IMM76I rooted,bootloader unlocked
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
I have the exact same problem! No clue what's causing this. I'm on AOKP M5 on rooted Galaxy Nexus. I can't find any setting to disable bug report creation, nor can I find anything about bug reports in the settings at all. I really hope someone can figure out what's causing these spontaneous bug reports (plus screenshots) to be generated.

Same issue
I just received my 4.0.4 update on Galaxy Nexus, and I am having the same issue. It randomly takes a snapshot of the lock screen and generates a bug report. Have they added some new hardkey combination that is too easy to trigger? I do have a case on, but I have always had it on, way before the update.

This is a manual bug report triggered by pressing both volume keys and the power button at the same time. It will vibrate once when you do it and then it takes a good minute or two for it to compile the report. The phone will then vibrate 3 times quickly when the report is ready, but only if the phone is awake and unlocked. So, for example, if you hit the power button to check the time and happen to press all three buttons or your TPU case (just an example) is holding down your volume buttons, then it will trigger then. You won't actually see the results until the next time you unlock the device. They are addressed to your default email address unless your ROM developer adds an email to them. Obviously being stock this would not be the case.
If you want to get rid of this feature, go to /system/bin and rename bugmailer.sh to bugmailer.sh.bak or delete it. Then reboot and no more bugmailer.
Source: http://rootzwiki.com/index.php?/topic/18671-Disable-bug-report-error-messaging?#entry488123

chandradithya said:
This is a manual bug report triggered by pressing both volume keys and the power button at the same time. It will vibrate once when you do it and then it takes a good minute or two for it to compile the report. The phone will then vibrate 3 times quickly when the report is ready, but only if the phone is awake and unlocked. So, for example, if you hit the power button to check the time and happen to press all three buttons or your TPU case (just an example) is holding down your volume buttons, then it will trigger then. You won't actually see the results until the next time you unlock the device. They are addressed to your default email address unless your ROM developer adds an email to them. Obviously being stock this would not be the case.
If you want to get rid of this feature, go to /system/bin and rename bugmailer.sh to bugmailer.sh.bak or delete it. Then reboot and no more bugmailer.
Click to expand...
Click to collapse
While I appreciate the fact that you are helping out, please do not take my responses from another forum and paste them here verbatim as your own.
Source: http://rootzwiki.com/index.php?/topic/18671-Disable-bug-report-error-messaging?#entry488123
Also of note for those having the issue on the 4.0.4 update, disabling USB debugging should now also disable the bugmailer.
Sent from my brain using human to phone transport technology.

ABQNM said:
While I appreciate the fact that you are helping out, please do not take my responses from another forum and paste them here verbatim as your own.
Source: http://rootzwiki.com/index.php?/topic/18671-Disable-bug-report-error-messaging?#entry488123
Also of note for those having the issue on the 4.0.4 update, disabling USB debugging should now also disable the bugmailer.
Sent from my brain using human to phone transport technology.
Click to expand...
Click to collapse
No offence to you. Seriously.
was annoyed with this issue, google searched it , opened a lot of tabs, found many posts never had answers,
I agree it was copy paste, sorry for not mentioning the source.
I edited them and linked it to your post on rootzwiki,
I was in a hurry then and rushed up and pasted on the threads where there was no proper answers.

I have the same problem
Hello guys.
I have the same problem. I have the Android 4.2 original from Google. I have the issue from Android 4.1 and I don't know what is the problem.

Drakonworld said:
Hello guys.
I have the same problem. I have the Android 4.2 original from Google. I have the issue from Android 4.1 and I don't know what is the problem.
Click to expand...
Click to collapse
See my full explanation here http://rootzwiki.com/index.php?/topic/18671-Disable-bug-report-error-messaging?#entry488123 (last post on the page). Simple answer, something is pressing all three buttons at once, be it a case or whatever. Either disable usb debugging to turn it off or see my link for instructions to disable just the bugmailer.
Sent from my brain using human to phone transport technology.

Milestone 5 Physical button light fix

I still saw a lot of people asking about a fix for this issue on the AOKP thread. I would post this there, but I don't have the privileges as of yet. Anyways for those of you that want the physical lights on, pull down your notification bar and set the brightness on max. Press/toggle the auto brightness button on and off several times. Saw a few people say 20 times. On your last press make sure you toggle the auto brightness on, then very quickly press the power button to turn the screen off, and then quickly press the power button again to go to your lock screen. Afterwards your physical lights should be working normally again. You have to repeat this step over again if you reboot your phone, but atleast this is a temp fix for those of you that want the lights on. I did not come up with this as I found it through a search, but a lot of people are still asking for a fix so I figured I'd post it.

+1 op

Confirmed working on CodeName.
Awesome. +1
Sent from my Epic Touch using XDA Premium App

Didn't even realize they were even broken. Fixed it for me though

Thanks man I'll try it out . I've been looking for a fix for that and haven't seen one till now. I've posted a few questions in the general thread but I never seem to get an answer. Thanks for helping another noob ! I've been experimenting quite a bit with AOKP, CM9, and Codename and I was wondering why the stock task killer isn't included in neither of the 3. They are amazing especially AOKP but my battery doesn't last me through work and I'm assuming its because I have some apps running in the background. Anyone know why the devs didn't include it or know how I can install it ? Just to be clear I'm looking to install the stock task manager w/ program monitor not the task killers from the market that don't work. Any help would be appreciated. Thanks guys !

Physical Keyboard stops working

Quite frequently, my glide's physical keyboard stops working. A reboot fixes it but is kind of annoying to do this once a day
This is a new phone (less than a week old) and I am trying to find out if this is a known issue and if there is a fix for it. If my phone is defective, I might be able to still get a replacement from newegg.
I notice that there was another thread in XDA on the same topic but it quickly moved on to discuss some other issue with no clear advice.
Thanks and appreciate your help,

urundai said:
Quite frequently, my glide's physical keyboard stops working. A reboot fixes it but is kind of annoying to do this once a day
This is a new phone (less than a week old) and I am trying to find out if this is a known issue and if there is a fix for it. If my phone is defective, I might be able to still get a replacement from newegg.
I notice that there was another thread in XDA on the same topic but it quickly moved on to discuss some other issue with no clear advice.
Thanks and appreciate your help,
Click to expand...
Click to collapse
Stops working all together or opens up different applications when you press a key? I had the latter. If it is the apps opening up double check you do not have any shift type button stuck as that would make it act funny and appear to not be working properly.
Tap on "ALT", "SHIFT", "SEARCH" see if that fixes it.

dudejb said:
Stops working all together or opens up different applications when you press a key? I had the latter. If it is the apps opening up double check you do not have any shift type button stuck as that would make it act funny and appear to not be working properly.
Tap on "ALT", "SHIFT", "SEARCH" see if that fixes it.
Click to expand...
Click to collapse
Thanks for the response. I went back to my old iPhone 3 (Yuck). Let me double check on that when I get home this evening.

urundai said:
Thanks for the response. I went back to my old iPhone 3 (Yuck). Let me double check on that when I get home this evening.
Click to expand...
Click to collapse
If it is launching Different apps then it is the Quick launch that is the cause. You can see what Shortcut is associated with which app go here:Settings -> Applications -> Quick Launch
Most Launch with Search + any key. Perhaps your search button is stuck.
JB

Mine has that problem as well usually requires a reboot as well but can't ever get it to just do it on command. U on a custom rom? Or stock?

If the random apps are opening, open the landscape keyboard and press the search button. If you accidentally press it and then you press a corresponding letter to open a certain app, it'll so that. And when you hit back, the phone thinks that you pressed the wrong letter key and has that quick open on. Just press search again. That's all lol
Sent from my SAMSUNG-SGH-I927R using xda premium

I also have the problem of physical keyboard that stops working. No random apps, it just stops working. What to do to fix the issue, aside from rebooting?
Thx

phatryan69 said:
Mine has that problem as well usually requires a reboot as well but can't ever get it to just do it on command. U on a custom rom? Or stock?
Click to expand...
Click to collapse
I am on stock. It's just annoying when it happens at least once in 2 days.
I am thinking of rooting it and installing a custom rom to see if that takes care of it. Will keep you all posted.
I might turn on the debugging level in the logs as well to see if I can find out what's going on. Given that this happens only every two days or so, not sure if that will help much but let me see.

antonyfirst said:
I also have the problem of physical keyboard that stops working. No random apps, it just stops working. What to do to fix the issue, aside from rebooting?
Thx
Click to expand...
Click to collapse
I am on Rogers stock ROM. At this point, it certainly looks like something to do with the software (will be hard to find several of us having the same hardware problem).

dudejb said:
Stops working all together or opens up different applications when you press a key? I had the latter. If it is the apps opening up double check you do not have any shift type button stuck as that would make it act funny and appear to not be working properly.
Tap on "ALT", "SHIFT", "SEARCH" see if that fixes it.
Click to expand...
Click to collapse
+1.
My keyboard stops working too, but this doesn't happen very often. I experience this about once in 3-4 weeks for now.

I have had this problem a few times as well (on stock AT&T).. QWERTY doesn't respond at all, reboot fixes it! Got me worried the first couple of times though

I continue to run in to this once in a while. I have tried pressing all kinds of keys (search, alt etc) with no success. At times, I see some of the keys working but not others.
Anyway, this looks like software / driver issue. Looks like reboot is the only cure so far.

issues with the at&t ics for captivate glide

so i'd like to collect the issues (and solutions) for the captivate glide's new official android upgrade (ice cream sandwich).
we all know about the keyboard backlight issue,but its already solved (thanks for it to the devs), moreover we have an opportunity for rooting, as well.
Apart from that I experienced that after a few seconds of black screen, "com.android.phone stops" after I receive or make phone calls. That is also can be solved by making a factory reset.
But I have a problem I couldnt solve yet: screenshot/screencapture. On gingerbread you had to hold home button while pressing the lock key. On ICS it doesnt work. I read that on ICS you should press volume down and lock key at the same time, but that doesnt work for me either. Do you know a solution for this?
I've got one more problem, but I'm not sure if its a fault of the ROM: on the stock web browser,everything works fine, but on google chrome, I cannot use virtual keyboard,nor copy/paste functions.
Thanks for your help

soadzoor said:
so i'd like to collect the issues (and solutions) for the captivate glide's new official android upgrade (ice cream sandwich).
we all know about the keyboard backlight issue,but its already solved (thanks for it to the devs), moreover we have an opportunity for rooting, as well.
Apart from that I experienced that after a few seconds of black screen, "com.android.phone stops" after I receive or make phone calls. That is also can be solved by making a factory reset.
But I have a problem I couldnt solve yet: screenshot/screencapture. On gingerbread you had to hold home button while pressing the lock key. On ICS it doesnt work. I read that on ICS you should press volume down and lock key at the same time, but that doesnt work for me either. Do you know a solution for this?
I've got one more problem, but I'm not sure if its a fault of the ROM: on the stock web browser,everything works fine, but on google chrome, I cannot use virtual keyboard,nor copy/paste functions.
Thanks for your help
Click to expand...
Click to collapse
Press and hold Power + Home button together for a screenshot.
Keyboard works fine for me on Chrome, as well as copy/paste. But mine can be a different scenario as i'm running NardROM with the LH2 kernel.

ninthsense said:
Press and hold Power + Home button together for a screenshot.
Keyboard works fine for me on Chrome, as well as copy/paste. But mine can be a different scenario as i'm running NardROM with the LH2 kernel.
Click to expand...
Click to collapse
Thanks a bunch! if i press them at the same time and hold them, it just works as a charm! Im wondering why I didnt figure that out by myself.
The chrome with virtual keyboard is still no better.. anyone has a tip?

If anybody knows how to get past KIES because it never recognizes my phone, I'd love to get ICS to load.

just use this: http://forum.xda-developers.com/showthread.php?t=1841502 It's what I am using and most people were using before the Official came out. No diffidence between the 2 version practically. Make sure you have CWM then flash. Oh and as always do a nandroid backup before. It is the only way back as well.

I'll admit it... I'm a n00b that this and don't want to brick my phone. Dare I wait till Samsung / AT&T get their stuff together and get the KIES & ICS issues fixed or do I try the link dudejb suggested? A clear step by step would be appreciated (no offense intended). I'm just not too technically savvy.

If you're new to android flashing and not comfortable with something like that, I wrote up a nice newb-friendly guide here that walks you through installing the 4.0.4 leak, as well as installing ClockworkMod Recovery, fixing the keyboard backlight issue, and rooting.
I'd say go for it, you'll be waiting quite some time just to see Samsung fix the keyboard light, let alone address your issue of kies not seeing the phone.

I'd like to chime in with another problem I've noticed. With Gingerbread, the physical keyboard worked just like the on-screen one: tap shift or alt to modify the next keystroke, tap twice to lock the modifier. With ICS (the official firmware installed via Kies), however, a single tap on the physical keyboard keeps modifying keystrokes until tapped again. Has anyone else experienced this? Since I have the force-closing problem with the phone, I'm planning on doing a factory reset. Maybe that will solve my keyboard problems.
Also, I can also confirm problems with the on-screen keyboard in Chrome. All the other browsers work fine, but the keyboard just won't show up in Chrome. Combine that with the physical keyboard problems I've been having and Chrome becomes essentially unusable.
On the plus side, my battery life seems better. It used to be that I couldn't go more than eight hours without the phone dying on me, but now it's still going strong at 20-30% after eight hours.

clpo13 said:
With Gingerbread, the physical keyboard worked just like the on-screen one: tap shift or alt to modify the next keystroke, tap twice to lock the modifier. With ICS (the official firmware installed via Kies), however, a single tap on the physical keyboard keeps modifying keystrokes until tapped again. Has anyone else experienced this?
Click to expand...
Click to collapse
I'm not having that problem with the LH2 update (checked in the stock browser and text messages).
Here's my list of bugs/complaints with the LH2 official update:
1. no keyboard backlight (I know there's a fix.)
2. occasionally getting "com.android.phone has stopped" after ending a call. (I've seen at least 4 people report this problem on this forum.)
3. email app display is blank after adding a email account (solved by changing font size, then it's fixed)
4. email app doesn't remember which view you selected after closing (i.e. standard/conversation view, always defaults back to standard view)

clpo13 said:
I'd like to chime in with another problem I've noticed. With Gingerbread, the physical keyboard worked just like the on-screen one: tap shift or alt to modify the next keystroke, tap twice to lock the modifier. With ICS (the official firmware installed via Kies), however, a single tap on the physical keyboard keeps modifying keystrokes until tapped again. Has anyone else experienced this? Since I have the force-closing problem with the phone, I'm planning on doing a factory reset. Maybe that will solve my keyboard problems.
Click to expand...
Click to collapse
I can confirm the problems with the keyboard's alt and shift keys. It's a pain

My physical keyboard works just like before. I haven't looked, but I imagine this is something you can set in the Input tab in Settings?
EDIT: It's not there, sorry. I also have the CRT-Off, Custom Boot Anim and Backlight fix mods installed. Perhaps that makes a difference?
Sent from my SGH-I927 using xda app-developers app

Evil Alex said:
My physical keyboard works just like before. I haven't looked, but I imagine this is something you can set in the Input tab in Settings?
EDIT: It's not there, sorry. I also have the CRT-Off, Custom Boot Anim and Backlight fix mods installed. Perhaps that makes a difference?
Sent from my SGH-I927 using xda app-developers app
Click to expand...
Click to collapse
I too had the keyboard problem. I traced it back to the keyboard app "Swiftkey3." If I use any other keyboard app (stock or not), the physical keyboard works as it should. If Swiftkey is enabled, the caps or alt keys lock on with one press. VERY annoying.
Other than that, I've experienced some txt messages coming in multiple times. Like sometimes more than 15 copies of one txt. Seems to have calmed down some since I moved from the official leak to NardROM 0.4, but I did have a txt last night come in twice. Maybe that one was on my friend's end and he actually sent it twice.
Right now, my main concern is battery consumption on NardROM 0.4. Seems a bit worse than when I was running the stock leak (rooted). Battery profile attached. I've barely used my phone today since unplugging it, yet plenty of drain. I have no idea why the phone is "awake" so much when the screen is off.

bakageta said:
If you're new to android flashing and not comfortable with something like that, I wrote up a nice newb-friendly guide here that walks you through installing the 4.0.4 leak, as well as installing ClockworkMod Recovery, fixing the keyboard backlight issue, and rooting.
I'd say go for it, you'll be waiting quite some time just to see Samsung fix the keyboard light, let alone address your issue of kies not seeing the phone.
Click to expand...
Click to collapse
I haven't tried to do anything yet because the link you supplied has in it this phrase which concerns me.... "First, make sure you have Kies installed, so that you have the correct USB drivers." I cannot connect to the phone using the latest KIES installed on my PC. Is there supposed to be KIES on my phone, because if there is, it's missing. Again, please be patient with me and thank you all for everybody's help.

clpo13 said:
With Gingerbread, the physical keyboard worked just like the on-screen one: tap shift or alt to modify the next keystroke, tap twice to lock the modifier. With ICS (the official firmware installed via Kies), however, a single tap on the physical keyboard keeps modifying keystrokes until tapped again
Click to expand...
Click to collapse
I experienced the same but I realised that it depends on the program you use. At some browsers it is the way you just described it, but with texting, and with the stock browser, everything is fine to me

bakerb316 said:
I haven't tried to do anything yet because the link you supplied has in it this phrase which concerns me.... "First, make sure you have Kies installed, so that you have the correct USB drivers." I cannot connect to the phone using the latest KIES installed on my PC. Is there supposed to be KIES on my phone, because if there is, it's missing. Again, please be patient with me and thank you all for everybody's help.
Click to expand...
Click to collapse
i have a difficult time connecting to my phone with Kies as well. Here are some steps to take that have helped me:
download the latest version of kies.
remove battery from phone for 30 seconds, then let it boot back up fully before plugging to computer (this was from samsung tech support)
uninstall kies, run ccleaner registry cleaner, reboot, reinstall kies.
download the 1.5.xx version of samsung USB drivers.
I've had to do all of those things to get Kies to see my phone.
and on a couple of computers, it just won't read it, at all.

euro1990 said:
Right now, my main concern is battery consumption on NardROM 0.4. Seems a bit worse than when I was running the stock leak (rooted). Battery profile attached. I've barely used my phone today since unplugging it, yet plenty of drain. I have no idea why the phone is "awake" so much when the screen is off.
Click to expand...
Click to collapse
Toggle off wi-fi and bluetooth, ya dingbat! :silly: Your phone is likely trying to re-sync BT connection and/or sending a wifi heartbeat, and/or searching for wifi network.

euro1990 said:
I too had the keyboard problem. I traced it back to the keyboard app "Swiftkey3." If I use any other keyboard app (stock or not), the physical keyboard works as it should. If Swiftkey is enabled, the caps or alt keys lock on with one press. VERY annoying.
Click to expand...
Click to collapse
How about that. I did have SwiftKey installed and enabled. I switched to another keyboard and it's working fine now. Strange that it would affect the physical keyboard like that.

bakerb316 said:
I haven't tried to do anything yet because the link you supplied has in it this phrase which concerns me.... "First, make sure you have Kies installed, so that you have the correct USB drivers." I cannot connect to the phone using the latest KIES installed on my PC. Is there supposed to be KIES on my phone, because if there is, it's missing. Again, please be patient with me and thank you all for everybody's help.
Click to expand...
Click to collapse
Simply having Kies installed on your PC should make sure you have the drivers you need, you don't actually need to run Kies. Follow the instructions for download mode, and see if you get a green OK in the 4.0.4 exe. If so, you'll be fine.

Apparently Samsung has heard enough complaints about the issues with ICS and the Glide, so they made this 'announcement' on their website.
AT&T Cell Phones: How do I update my Samsung Captivate Glide to Android 4.0 Ice Cream Sandwich?
The update for the Samsung Captivate Glide has been put on hold while Samsung works to optimize the update for our users.
Here's would be the link if I would be able to attach it.
Not too sure what those 'optimizations' entail (Keyboard back light I'd assume to be one of them), or if Kies connectivity is one as well because I had a chat with one of their online support agents and he said this...
"As there is huge demand on the Kies server and that is why the update is put on hold. As the Kies server is busy the phone would not be detected."
Sounds fishy to me, but plausible.

a new update for chrome has been out today! now the onscreen keyboard is visible and works well!

[Q] Sporadic Black Screen of Death, any solution?

I have the above issue with stock 4.2. Sometimes the screen goes blank (like a dark Grey back light), the phone is still on, but I can't get into it anymore. It registers touches etc, just the screen doesn't get back.
Flashed clean stock Image, factory reset and data restore.
Only battery pull helps. Happens 1 or 2 times per day in various situations (texting, browsing, whatsapp). Luckily I don't have any of the other 4.2 problems, except the missing December in Contacts. The phone is otherwise snappy as hell with 167 apps installed, recent tasks and swiping to close apps are instant.
Did anyone find a solution yet?
Sent from my Galaxy Nexus using Tapatalk 2

nomad4ever said:
I have the above issue with stock 4.2. Sometimes the screen goes blank (like a dark Grey back light), the phone is still on, but I can't get into it anymore. It registers touches etc, just the screen doesn't get back.
Flashed clean stock Image, factory reset and data restore.
Only battery pull helps. Happens 1 or 2 times per day in various situations (texting, browsing, whatsapp). Luckily I don't have any of the other 4.2 problems, except the missing December in Contacts. The phone is otherwise snappy as hell with 167 apps installed, recent tasks and swiping to close apps are instant.
Did anyone find a solution yet?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Same thing here, never had an issue with 4.1.2 but now it happens 2-3 times a day
Sent from my Galaxy Nexus using xda premium

same me..
this is really annoying..anyone tried a clean install of 4.2 to see if its get solved? im bored to wipe..

andQlimax said:
same me..
this is really annoying..anyone tried a clean install of 4.2 to see if its get solved? im bored to wipe..
Click to expand...
Click to collapse
Let me know how that works... I have been having this problem also. Screen is blank every 2 days it happens once. Ever since 4.2 update. Before that I had no issues like this.
Also un related but I've started to notice faint horizontal lines in my screen. I use auto brightness. Is this normal or return for warranty?

i can confirm this happens to me too.
4.2 stock only rooted with custom recovery.

Same here folks, It may a bug in the 4.2 builds since Sprint did not officially release 4.2 yet.

This happens on my GSM model. It's never been rooted, and only started doing this after the 4.2 OTA.
You can shut the phone down without pulling the battery. Press the power button once to lock (or just wait until it locks on its own). Press the power button again to bring up the unlock screen, unlock and then long-press the power button. A short vibration tells you when the shutdown menu is up, and the SHUT DOWN button is across from the midpoint of the volume rocker, so you can press it without seeing it. The display works fine when it's powered back up again.
I have a theory that the problem is related to another bug in the auto-brightness in 4.2. The display always goes to maximum brightness for a split second before going black. I have set my phone to manual brightness for the last day or so and have not seen the problem again (yet).

same issue here, I'll try to keep the brightness to manual to see if it works

chanchan305 said:
same issue here, I'll try to keep the brightness to manual to see if it works
Click to expand...
Click to collapse
Manual brightness didn't work for me. Everything I have read seems to lead to something wacky in source. I finally went back to 4.1.2. It hurt to go backwards,but no more issues. I'll come back when it is fixed.
By the way, I did discover that if I was at my computer when it happened, I could reboot the phone using adb.

MondoMor said:
This happens on my GSM model. It's never been rooted, and only started doing this after the 4.2 OTA.
You can shut the phone down without pulling the battery. Press the power button once to lock (or just wait until it locks on its own). Press the power button again to bring up the unlock screen, unlock and then long-press the power button. A short vibration tells you when the shutdown menu is up, and the SHUT DOWN button is across from the midpoint of the volume rocker, so you can press it without seeing it. The display works fine when it's powered back up again.
I have a theory that the problem is related to another bug in the auto-brightness in 4.2. The display always goes to maximum brightness for a split second before going black. I have set my phone to manual brightness for the last day or so and have not seen the problem again (yet).
Click to expand...
Click to collapse
bfprd0 said:
Manual brightness didn't work for me. Everything I have read seems to lead to something wacky in source. I finally went back to 4.1.2. It hurt to go backwards,but no more issues. I'll come back when it is fixed.
By the way, I did discover that if I was at my computer when it happened, I could reboot the phone using adb.
Click to expand...
Click to collapse
I experience this issue, but not that frequent. Once every 4 or 5 days, i don't know. I've managed to pull a logcat today as i was near of pc, as posted before, adb/phone is responsive, it even locks the screen normally, there was nothing useful on dmesg. I don't normally use auto-brightness, but enabled it a little while ago, although now i'm not sure if it was enabled the first time it happened. This last time, it wasn't enabled, that I'm sure.
It happened to me both when I was using XDA-app. I have almost 0 user apps installed right now, also uninstalled XDA. Reporting back in a few.

the issue is related to location services
the "bug" has been reported to google http://code.google.com/p/android/issues/detail?id=40140
for a temporary fix turn off services/apps that track you e.g. latitude

ogdobber said:
the issue is related to location services
the "bug" has been reported to google http://code.google.com/p/android/issues/detail?id=40140
for a temporary fix turn off services/apps that track you e.g. latitude
Click to expand...
Click to collapse
huh... i also don't have location services active nor gps. i never do.
and, in our case, the phone is still on, it doesn't reboot, just the screen is black. it's not the same issue.
edit: if i manage to hit it again, my next step will be unroot. full stock.

bk201doesntexist said:
huh... i also don't have location services active nor gps. i never do.
and, in our case, the phone is still on, it doesn't reboot, just the screen is black. it's not the same issue.
edit: if i manage to hit it again, my next step will be unroot. full stock.
Click to expand...
Click to collapse
ok...star this issue https://code.google.com/p/android/issues/detail?id=40019