I've had this problem on my GSII (SGH-i777) since playing around with ICS roms, in both AOKP and CMD.
What happens is, after locking it, or a program is supposed to wake it from a blank screen, nothing happens when pressing the power button. The phone is still on and the buttons on the bottom still light up and I can feel vibrations and sounds, but I cannot get the screen to come back on without rebooting.
I'm not sure what causes this and it seems to feel semi random, but I suspect it may be connected to the locking animation in some way introduced in ICS (the emulation of turning off a CRT monitor).
I'm wondering if anyone else has run into this problem and knows a good fix to avoid it (other than going back to stock firmware).
What app are you using that is supposed to wake your phone? Just my opinion but it sounds like an issue with the app.
PS. Crt off animation was introduced well before ics.
ThomasBags said:
I've had this problem on my GSII (SGH-i777) since playing around with ICS roms, in both AOKP and CMD.
What happens is, after locking it, or a program is supposed to wake it from a blank screen, nothing happens when pressing the power button. The phone is still on and the buttons on the bottom still light up and I can feel vibrations and sounds, but I cannot get the screen to come back on without rebooting.
I'm not sure what causes this and it seems to feel semi random, but I suspect it may be connected to the locking animation in some way introduced in ICS (the emulation of turning off a CRT monitor).
I'm wondering if anyone else has run into this problem and knows a good fix to avoid it (other than going back to stock firmware).
Click to expand...
Click to collapse
Try turning off CRT in system setting / ROM Control / General UI / uncheck CRT off animation. I have it off and never have a problem in AOKP
This guy probably didn't wipe everything before posting. Yes this includes your data.
Sent from my MB860 using Tapatalk 2
Related
I've searched with several different search strings and haven't found an answer to this question, so here goes;
When I place a call and bring the phone to my ear the screen turns off (dims?). At the end of the call after I bring the phone away from my ear, it takes several seconds for the screen to turn back on, sometimes it doesn't turn back on unless I press the power button.
First, is this the normal behavior for the phone app on the I777?
Second, is there a setting somewhere to change the delay for the "screen on after a call" (I know there is a setting in settings-display for screen time-out).
I hate to make the comparison, but on my iPhone (No flaming please, I'm reformed) the screen turned off and on very quickly and I just wonder what I need to do to get that kind of response on the SG2, during the phone call.
BTW, I'm running UnNamed 2.2.1 (Gingerbread 2.3x) with Entropy's kernel.
Thanks for any help.
Clean your screen.
You using a case? Maybe it's partially blocking the proximity sensor.
mbamberg said:
I've searched with several different search strings and haven't found an answer to this question, so here goes;
When I place a call and bring the phone to my ear the screen turns off (dims?). At the end of the call after I bring the phone away from my ear, it takes several seconds for the screen to turn back on, sometimes it doesn't turn back on unless I press the power button.
First, is this the normal behavior for the phone app on the I777?
Second, is there a setting somewhere to change the delay for the "screen on after a call" (I know there is a setting in settings-display for screen time-out).
I hate to make the comparison, but on my iPhone (No flaming please, I'm reformed) the screen turned off and on very quickly and I just wonder what I need to do to get that kind of response on the SG2, during the phone call.
BTW, I'm running UnNamed 2.2.1 (Gingerbread 2.3x) with Entropy's kernel.
Thanks for any help.
Click to expand...
Click to collapse
Ironically I had the same experience in UnNamed to I assumed it was just the nature of GB. It may very well have been as I don't have that issue with ICS based ROMS. And I like the dialer better to boot.
audiophan said:
Ironically I had the same experience in UnNamed too I assumed it was just the nature of GB. It may very well have been as I don't have that issue with ICS based ROMS. And I like the dialer better to boot.
Click to expand...
Click to collapse
OK,
I'm in the throes of upgrading to an ICS ROM, so maybe I'll just go ahead and see if that fixes the problem.
Thanks for the answers
I think its a sensor issue having to due with how long it waits to scan again after light levels are changed. No idea what stock settings are but I can say I don't have a problem with it on AOKP.
I have Speed Rom 5.1 on my Amaze. When I am finished with a call, the screen stays black. I try to hit the power button, but nothing happens. I have to remove my battery in order to reboot. Can someone shed some light on why this happening? I am thinking that it may have something to do with my CPU Tuner settings, but I am not sure.
mrcash101 said:
I have Speed Rom 5.1 on my Amaze. When I am finished with a call, the screen stays black. I try to hit the power button, but nothing happens. I have to remove my battery in order to reboot. Can someone shed some light on why this happening? I am thinking that it may have something to do with my CPU Tuner settings, but I am not sure.
Click to expand...
Click to collapse
Probably that or a bad flash, just reflash, see if it solves the issue.
Most likely it's something simple, like an issue with your proximity sensor. I know there was an app that could calibrate that but I forgot what the app was.
Stock Rom - Black screen while phoning
There is a similar problem on my wife's phone with a stock rom (not rooted Amaze from T-Mobile). When making or accepting a call, the screen will instantly go off even without leaning the phone against anything and won't turn on unless the power button is pressed. Sometimes the screen would turn on by itself after a while after the other phone was hanged.
I've downloaded AndroSensor app: the proximity value does't change even when touching the area near the earpiece. It keeps showing ( 0.5mA ) 3.5 in.
I've found a thread which is there since april 2012 and describes quite a similar problem.
okay.. i just the original post date for this thread.. please don't bring back threads that are 6 month's old which issues might have been solved already since no ones been posting in it for 6 months...
(anyways) this is what i was gonna say
on my current s3 when my phone is placed to my ear it cuts off the display.. and if you pass your hand anywhere near the sensor's to the top near the camera it cuts off the display.. maybe there's a feature like that enabled on the stock rom also.. or you could possible check with the system settings to see "screen" on/off settings in display or power saving mode.. or something...
Thanks for the answer. I didn't notice that the thread was that old. I think I will keep up a newer one. But the current issue isn't likely to have been solved.
The problem doesn't seem to be triggered by wrong sensor measures (because the screen will go off even after disabling the sensor) nor does it depend on the rom version (same thing on the CM10).
Resolved:
It will sound stupid but I have found a simple solution:
I have just wiped the screen in the upper left corner where the proximity sensor is located and it started behaving normally. Though I don't use any protection tape on the screen it seem to have become less sensitive because of mud or sweat.
Just bought one... have the newest update but my wifi still shuts down once I hit the power button and i am unable to find a fix. Second every now and then, and becoming more frequent, when i touch the screen a black oblong shape will flash black ( almost like a thick lighting bolt shape) about a third of the screen. Has anyone else had this happen? Also The touch screen itself wont respond properly, I have to touch multiple times sometimes to get a response.( not to frequent but enough to be an annoyance ) lastly it will power off a random at least 1-2 times daily. Other than that I like it, just has a few bugs to work out.
The screen flickering and wifi have always been bugs with both Sony Tablets with the later being fixed in release 5, or at 'seast it should've been, if thats what your on.
shouldnthaveboughtthis said:
Just bought one... have the newest update but my wifi still shuts down once I hit the power button and i am unable to find a fix. Second every now and then, and becoming more frequent, when i touch the screen a black oblong shape will flash black ( almost like a thick lighting bolt shape) about a third of the screen. Has anyone else had this happen? Also The touch screen itself wont respond properly, I have to touch multiple times sometimes to get a response.( not to frequent but enough to be an annoyance ) lastly it will power off a random at least 1-2 times daily. Other than that I like it, just has a few bugs to work out.
Click to expand...
Click to collapse
For the wifi problem you can try installing "Advance Wifi Lock" (google play).. just install the free version, that should fix your problem.. let me know if it work!
What device?
If it is the Sony Tablet S, factory reset to fix most issues but there will be a few issues like screen flickering hidden in the settings while changing notification sounds and a few system server issues where the OS crashes to the boot animation and then System UI crashes, system server crashes in to a bootloop of crashes and stuff.
So system server/system UI is a bug sometimes.
Sent from my Sony Tablet S using xda premium
I've been experiencing for some time now some random freezes when trying to face-unlock the phone. When pushing the power button to wake the phone, it displays the unlock screen but the box in the screen where your face (or whatever the front camera catches) blacks out, while the rest of the screen is normal (I can see the clock, the notification bar and the emergency call), also the leds for back and menu light up. And the phone justs stays like that, all the leds lighted up and the screen on. The home button doesn't work and the power button only works if I hold it down (it powers down / restarts the phone).
This has happened to my phone from some time ago, its purely random and it always happens when I try to unlock the phone. I haven't had any issues while using the phone nor strange bootloops or sudden reboots. I'm currently on stock XXEMB5 with Speedmod Kernel k2-13 and some apps removed, mainly yahoo widgets and some Samsung apps (I think I just removed all the hubs: game hub, social hub, etc...).
I red the bad eMMs symptoms, but it doesn't seem to be the same. If I had to guess, I would say its something with the camera, but right now I don't know for sure... Anyone has any idea where could be the problem?
Favourite culprit would be a non-standard kernel, wipe the phone and return to fully stock to test.
Your collection of mods and custom changes to rom are probably unique, if it doesn't freeze when stock then add changes one at a time until it happens again.
In two different AOKP roms (AOCP, PACman), I have a problem where if I'm on a call and forcefully turn the screen off by pressing the power button (as opposed to by the prox sensor or by timeout), the phone reboots. Interesting, if there's audio on the call, it will continue to play as the shutdown animation is playing.
I have the accessibility setting to end calls with the power button turned OFF. I can't think of any other settings which would affect this.
I tried searching on this symptom, but didn't find anyone with this issue. I clean installed both ROMs, but AOKP seems to be a common denominator. Anyone have advice for me?
Does it ever reboot at other times after you've pressed the power button, or is it only while in a call? I recently had a problem where the phone would reboot after I turned it on. I was on CM and went to SHOStock and it still did the same! I figured, hell, after two different ROMs and it still acting the same, maybe it was hardware. Ended up taking the phone apart and there was some gunk around the inside part of the power button keeping it held in too far and triggering the reboot after a few seconds. After removing the button and carefully cleaning it (it's very small), I now no longer have a reboot problem on either CM or SHOStock.
sbrown23 said:
Does it ever reboot at other times after you've pressed the power button, or is it only while in a call? I recently had a problem where the phone would reboot after I turned it on. I was on CM and went to SHOStock and it still did the same! I figured, hell, after two different ROMs and it still acting the same, maybe it was hardware. Ended up taking the phone apart and there was some gunk around the inside part of the power button keeping it held in too far and triggering the reboot after a few seconds. After removing the button and carefully cleaning it (it's very small), I now no longer have a reboot problem on either CM or SHOStock.
Click to expand...
Click to collapse
I've only had it happen so far when turning the screen back on during a call. If I don't force the screen off in the first place, the phone will happily turn the screen on and off due to prox sensor. It will also time out and let me turn it back on without the power button with no issue. Because of this, I don't believe it's a mechanical issue. I didn't have this problem until trying AOKP ROMs, the timing is too coincidental.
Based on what I'm seeing with the boot animation, it isn't a full reboot (I don't see the SGS II logo, for example). I didn't even know that rebooting only the OS was possible.
I assume there are logs I can check to help figure out what's going on, but I don't know where to find them.
I found a string of posts in the Carbon thread: http://forum.xda-developers.com/showthread.php?p=46998058&highlight=just+carbon+reboots#post47133798. Same symptom, but different trigger. I tried, I can rotate the camera just fine. I'm currently running the 10/31 nightly of PACman, guess I'll update past 11/2 later today and see what happens.
11/6 was a bust (lots of FCs after a clean install), so now I'm trying 11/10, 11/4, or 11/5.
Initial results with 11/10 show that the problem is fixed; gonna restore my old ROM, go through the TiBu dance, and see what happens when I finish setting up 11/10 completely. Maybe it's something I'm doing.
OK, 11/10 fixed my primary issue. Further, I used to have pretty nasty screen-on lag that I couldn't fix even after messing with the CPU and I/O profiles. Hurray!
Based on my experience this may affect other AOKP based ROMs (like Carbon or AOCP), but it might have been present in pure CM (CyanogenMod) - hard to tell. Hope this helps someone else.
****, it's back. Must be something I'm doing. The quest continues...