Hi there,
I currently have a problem with my GNEX - whenever I get a call the screen won't turn on. I can hear the ringtone and the notification LED is blinking. When I push the power button, then it takes 3 - 4 seconds and the screen turns on. It only happens during the call, right after the screen immediatly turns on.
I've experienced this on AOKP and XenonHD now, on XenonHD I tried it with the latest AK kernel & fancy kernel - still the same. I got no clue what it could be, I just uninstalled avast! Mobile Security and rebooted the phone: no change.
Any ideas?
Greetz
// j_dee
j_dee said:
Hi there,
I currently have a problem with my GNEX - whenever I get a call the screen won't turn on. I can hear the ringtone and the notification LED is blinking. When I push the power button, then it takes 3 - 4 seconds and the screen turns on. It only happens during the call, right after the screen immediatly turns on.
I've experienced this on AOKP and XenonHD now, on XenonHD I tried it with the latest AK kernel & fancy kernel - still the same. I got no clue what it could be, I just uninstalled avast! Mobile Security and rebooted the phone: no change.
Any ideas?
Greetz
// j_dee
Click to expand...
Click to collapse
I also have a similar problem on Stock firmware (with Franco Kernel).
For me the cause for the screen not displaying when I receive a call is, something related to my cell service provider (Airtel India).
What happens is when ever I make a call or send an sms or use GPRS, after the service a message from my service provider will be displayed saying that how much I have been charged. If didn't discard that message either by clicking "OK", next time when ever I get a call my screen wont turn but the LED blinks.
I either use power button or screen swype (PGM2) to receive the call.
Exactly I don't which app/kernel is the culprit but at least in my case it is the cell service provider message which is creating the problem.
If I close the service message then my phone works normal. Hope this helps...
Hey raj,
good idea, but if that was the case then the problem should not occur after a reboot... Unfortunately it does. I'm certain that it was alright with the stock rom. Somewhere I read that undervolting can cause such an issue, but I'm using the default kernel values. Btw I use the Trickster to adjust the performance...
Greetz
// j_dee
Sent by XDA app from my Samsung Galaxy Nexus
Ok it seems i figured it out by reflashing the phone step-by-step. The problem is lockscreen rotation. When the lockscreen is locked in landscape mode then this problem occurs. LS rotation was enabled right after flashing the stock launcher with rotation enabled, so maybe it's got something to do with it.
Now LS rotation is disabled everything's working properly.
:banghead:
Greetz
// j_dee
Sent by XDA app from my Samsung Galaxy Nexus
Related
Just installed Cyanogen 6.1.2 with the stock kernel (savage's wouldn't pass validation in recovery for...well idk why. In fact, if anyone knows what is causing this, help would be appreciated.)
This issue wasn't occurring earlier today (before I flashed Cyan), but now when the screen is off and I push the power button to bring up the lock screen, it will either:
A) Work just fine.
B) The buttons on the bottom will light up, and nothing will happen.
C) There will be about a 5 sec. delay, and then the lock screen will come up.
It's reeeeally bugging me, and ruining my cyanogen experience :/
Please and Thank you!
I have the same problem on 6.1.1. So far I have uninstalled widget locker, removed my custom brightness profile and I'm currently testing the unlock delay under cyanogenmod settings. It seems to happen less when I have the unlock timeout set to immediate. I'm curious if your screen slowly dims before turning off when you hit the power button, out if it turns off immediately like a sense rom?
Sent from my PC36100 using XDA App
Yes, mine has been slightly dimming everytime as well. I'm wondering how common this is.
Sent from my PC36100 using XDA App
Try and set your lock timeout delay to immediate and let me know if you see improvement. Also, if you haven't figured out yet, the touch screen still works and you can unlock by swyping where your slider would be.
Sent from my PC36100 using XDA App
That seems to have fixed it to a point. It's still kind of intermittent, but for the most part there is no more issue. The strange dimming still occurs when locking though.
I've noticed that sometimes when I unlock my device I have a black screen with only the "multi-task" button and the status bar visible. It will stay like this until I "lock" the phone and unlock it again. Touching the "multi-task" button makes the rest of the buttons appear but touching them still doesn't make the screen respond. I have noticed this on both stock and custom rom. Has anyone else had this problem? Any ideas on a fix or cause?
I am using the Virgin/Bell Canada GSM version.
Thanks
ps. I've posted a pic to give people an idea of what I'm getting....as it may seem unclear in my explanation.
At first this sounded similar to a problem I had.. I installed Wave Launcher, which for some reason did not play well with my phone. I would unlock the screen and the screen would immediately go black as if it had shut off, but I could still push buttons and receive haptic feedback. I had to have someone call me and delete the app while I was in the call.. it sounds kind of similar but not really.. my first guess would be some sort of problem with an app being incompatible.
joshnichols189 said:
At first this sounded similar to a problem I had.. I installed Wave Launcher, which for some reason did not play well with my phone. I would unlock the screen and the screen would immediately go black as if it had shut off, but I could still push buttons and receive haptic feedback. I had to have someone call me and delete the app while I was in the call.. it sounds kind of similar but not really.. my first guess would be some sort of problem with an app being incompatible.
Click to expand...
Click to collapse
I wanted to pass this on...I was reading in the Team Kang rom that there is a "bugfix version: app navigation menu icons no longer disappear after unlocking phone". So I hope this is what relates to my problem and has been "fixed"!
I did a quick search but didn't find anything on this. For whatever reason, whenever I switch apps from the drop down notification menu, it forces me to input my lock screen pattern, even when I have the lock screen toggled off. I have my settings set to auto lock after 1 min, but this happens whenever I switch apps, even before a minute has passed.
Is this a known issue? Is this happening to anybody else? Is there a fix?
Thanks.
Edit: I'm still on 4.02. It hasn't updated to .04 yet.
No one?
:T
Has this always been happening or did you install/flash something before it started happening?
Sent from my Galaxy Nexus using XDA
I just got my GN yesterday, and it updated by itself to 4.02.
It's been happening ever since I turned on the lock screen. It goes away when the lock screen is turned off. But it's bizarre that it would ask for the lock pattern every time I switch apps from the notification drop down. It doesn't ask for the pattern if I were to switch apps with the App Switcher button.
Really perplexing...
Hate to keep bumping this, but this is just incredibly bizarre.
Can someone test on their GN if the same happens? Turn on a lock screen input, anyone will do. I happen to have the pattern lock. And try to switch between apps or alerts from the pull down notification menu (you can send yourself an email or something, or turn on the music player) and see if you are forced to put in your pattern/passcode/etc before you can switch over.
I have to put in my pattern to unlock the phone every single time I switch apps ONLY from the pull down menu. It's bizarre. If I switch apps from the App Menu, it doesn't do this.
I don't know what's going on. Is this a "feature" of ICS? Seems a bit overkill on security. Or do I actually have a faulty phone (but it seems software related?).
Any help would be great. If need be, I'll make a video to demonstrate what I'm talking about.
I had this problem on CyanogenMod. Change the lock screen to what you want, and then reboot. It should be fixed. If you don't do a reboot for some reason it gets confused.
Yes happens to me sometimes too on both 4.02 and 4.04 stock. I don't use a pattern lock but it just fades out and when I turn screen back on it's lockscreen.
Never had this problem. That is weird. I suggest flashing a stock image and see if it still happens. Make a nandroid first of course but throw it away and make a new nandroid if problem goes away.
bow chicka wow wow.
gravis86 said:
I had this problem on CyanogenMod. Change the lock screen to what you want, and then reboot. It should be fixed. If you don't do a reboot for some reason it gets confused.
Click to expand...
Click to collapse
I will try this. Thanks for the suggestion. Hopefully it will work. Will update.
gravis86 said:
I had this problem on CyanogenMod. Change the lock screen to what you want, and then reboot. It should be fixed. If you don't do a reboot for some reason it gets confused.
Click to expand...
Click to collapse
Yes, this solved it. Thank you! Oh, Ice Cream Sandwich.
I spoke too soon. It's back. I noticed when I toggle the lock screen off, the problem exists. But if I toggle the lock screen on, the problem goes away.
So it may be an issue with the widget itself. I'm using "No Lock" (https://play.google.com/store/apps/details?id=org.jraf.android.nolock&hl=en)
I'm gonna test other toggle widgets to see if it's app related.
onthecouchagain said:
I spoke too soon. It's back. I noticed when I toggle the lock screen off, the problem exists. But if I toggle the lock screen on, the problem goes away.
So it may be an issue with the widget itself. I'm using "No Lock" (https://play.google.com/store/apps/details?id=org.jraf.android.nolock&hl=en)
I'm gonna test other toggle widgets to see if it's app related.
Click to expand...
Click to collapse
So.. it's a third party app you're using and not the stock ics lockscreen..
It would've been wise if you told us that on the first post
qtx said:
So.. it's a third party app you're using and not the stock ics lockscreen..
It would've been wise if you told us that on the first post
Click to expand...
Click to collapse
Yes that would have been good info to have, but I am not running anything custom on my lock screen (though I am on CM) and had this same problem.
I had to reboot the phone after every time I changed the lock screen from anything to anything or I'd run into problems. When changing from no lock screen to a lock screen, I would lose notifications when waking the screen up if the notification was for the last app open.
For example, I was in the Messaging app and locked the screen, without going to the home screen first (so if I were to unlock the app would be right there). Then I received a text and notification worked. I pressed the button to wake the phone and the lock screen showed up (pattern unlock) and the notification for my new text message in the notification bar disappeared. But I hadn't even unlocked so I could get to the app yet...
Hi,
Strange problem with my note 2.
My phone doesn't vibrate when receiving a text message...
I can't see any settings to change when the phone should vibrate or not when on silent.
Any help would be greatly appreciated.
Andy
weird innit....
in the messaging app, go to settings and scroll down, under "notification settings" you can enable vibrate
Seems to be a bug
I have the same issue, but it is only an issue when the screen is off. If the screen is on, the vibrate feature works as the settings I have indicate it should. It appears to be a bug.
Searched high and low and there isn't a fix that I could find, so I just used Tasker (app) to set the phone to vibrate whenever a text message is received. Does the trick, now it vibrates on SMS receipt whether the screen is on or off.
mattytj said:
I have the same issue, but it is only an issue when the screen is off. If the screen is on, the vibrate feature works as the settings I have indicate it should. It appears to be a bug.
Searched high and low and there isn't a fix that I could find, so I just used Tasker (app) to set the phone to vibrate whenever a text message is received. Does the trick, now it vibrates on SMS receipt whether the screen is on or off.
Click to expand...
Click to collapse
I have the same issue on my T-Mobile Note 2 running a ported international ROM. It's driving me insane! :crying:
Thanks for the idea with using Tasker. I'm going to give that a try until I find an updated ROM release.
hi all,
bit of a strange issue with BFC on my note2 4G
about a week ago, i noticed nfc was off, i tried to turn it on from notification panel, but opton was just not responding, so had to turn it on in settings. turned it off after use and was ok.
next time i went to turn it on from notification panel, it went green then i get a message saying
Unfortunately system ui has stopped responding.
now it does it every time i try to turn it on from notifications or it is freyed out as per before.
has anyone else noticed or had this issue? or has a fix?
cheers
device details
model N7105T
stock 4.1.2 rom
rooted
baseband N7105TDVDMA1
build JZ054K.N7105TDVDMB1
kern 3.0.31-774241
fliptechnologies said:
hi all,
bit of a strange issue with BFC on my note2 4G
about a week ago, i noticed nfc was off, i tried to turn it on from notification panel, but opton was just not responding, so had to turn it on in settings. turned it off after use and was ok.
next time i went to turn it on from notification panel, it went green then i get a message saying
Unfortunately system ui has stopped responding.
now it does it every time i try to turn it on from notifications or it is freyed out as per before.
has anyone else noticed or had this issue? or has a fix?
cheers
device details
model N7105T
stock 4.1.2 rom
rooted
baseband N7105TDVDMA1
build JZ054K.N7105TDVDMB1
kern 3.0.31-774241
Click to expand...
Click to collapse
I have the same problem.
I initially tried to use SBEAM to send some files between my Note II, and my friends S4.
Then, I tried to turn it OFF, and same error occurs.
I also turn it off in the settings without a problem, but it automatically turns back on.
Which I really don't know why.
Hopefully this gets a fix.
fliptechnologies said:
has anyone else noticed or had this issue? or has a fix?
Click to expand...
Click to collapse
Known issue. (Not sure if Samsung knows this, the issue keeps recurring even in recent updates)
I'm not sure if there is a fix, but a workaround which works for me,
1) Turn off the NFC manually
2) Replace the NFC icon from notification panel with some other unused icon (say blocking mode)
3) Restart Phone
4) Add NFC notification panel icon back and now it should be okay and working for sometime.
5) I don't know what causes it. But repeat step 1-4 when System UI hangs and throws error.
ysrini said:
Known issue. (Not sure if Samsung knows this, the issue keeps recurring even in recent updates)
I'm not sure if there is a fix, but a workaround which works for me,
1) Turn off the NFC manually
2) Replace the NFC icon from notification panel with some other unused icon (say blocking mode)
3) Restart Phone
4) Add NFC notification panel icon back and now it should be okay and working for sometime.
5) I don't know what causes it. But repeat step 1-4 when System UI hangs and throws error.
Click to expand...
Click to collapse
cheers another method i found was
turn nfc on and off manually about 5 times from the wifi menu in settings
then the icon works