I have this problem with my S4 Active, and I had it with my Note 2, but I have never managed to find out why. The S4 is on the official ROM, only rooted, while the Note 2 had different ROMs: When I'm using the phone for surfing, or whatever, so the display is on, I don't get the incoming call screen where I can slide to answer or reject a call. I have to turn off the phone with the power button and wait for 3-4 seconds, and then the display will come on and show me the call screen. I have tried changing dialers, between original and a couple of different third party dialers, but it doesn't change anything. Has anybody else seen this, and do you know the reason or the cure?
Turned out to be Gesture Control, in all probability.
Related
Hi all. Got my first ATIV S Neo with Sprint a couple weeks ago, had graphical corruptions, and random reboots, replaced it for another.
This one works much better, but there are some issues I'm seeing (nitpicking?) and I'm not sure if I have another defective handset or if this is just WP8, or if this is common to just this handset. Came from an HTC arrive on WP7.5 and things were pretty stable.
1) Occasional live tile animation stuttering; If I, for instance, go into the messages hub, sometimes the live tile swing animation will lock for half a second and then immediately pop into the message hub. Happens loading other apps too.
2) Occasional lock screen weirdness;
2a) very rare; press power button, screen comes on, screen fades out like the phone lost power but not to backlight, then backlight shuts off, pressing the power button again, everything works fine.
2b) occasional; in a dark room, press the power button to wake to lock screen, press again to turn off. screen/backlight goes out, backlight comes back, then goes out, then quickly comes back and back out.
3) in IE, typing in the address bar, text input freezes as it brings up suggestions from bing. (type "google.com" and get "gole.com"). disabling search suggestions makes it go away.
4) Text notifications stop working; sometimes the text notification sound stops playing (vibrate remains working). Reboot corrects it. Have also had it where the vibrate alert goes away and not the sound.
Anyone else seeing these? Are these known or is this phone also messed up?
Haven't seen those on my (open-market GSM) ATIV S, but there were a handful of glitches when I first got the phone. Those were corrected in the first big fiormware update from Samsung in my case, but I had to wait a few months for it.
GoodDayToDie said:
Haven't seen those on my (open-market GSM) ATIV S, but there were a handful of glitches when I first got the phone. Those were corrected in the first big fiormware update from Samsung in my case, but I had to wait a few months for it.
Click to expand...
Click to collapse
Thanks, that makes me feel a little more comfortable. These problems really don't feel like hardware to me, since they're fairly infrequent. I might have to stop by the sprint store and test the display model out a little.
???
I'm having quite a few issues with my ROM'd Z phone using Paranoid. I've recently updated to the latest version as soon as I was alerted.
1. The lock screen freezes, or rather becomes limited in responsiveness. I use the swipe up to unlock. When I swipe up, the clock/notifications just bounces and eventually the screen goes dark, then off. Sometimes I can reset using the power menu, but often the screen is totally unresponsive so I have to do a hard reset. On occasion I have to reset multiple times consecutively because it locks up immediately after boot... until its finally usable again. https://drive.google.com/open?id=0B7OGcalUJSgHblZob2Q2eHNkLU0
2. The phone gets hot in my pocket. When I notice this, often it has unlocked, turned on GPS, turned on the LED, taken photos and opened apps, or a combination of things. Sometimes even made a phone call, either to a contact or a recent from the log.
3. Recently I noticed it randomly ghost selecting right in front of me. I was unable to unlock and had to hard reset the phone.https://drive.google.com/open?id=0B7OGcalUJSgHVmJhQ0FOUDdLQkE
4. I am not getting SMS alerts from Optus 321 telling me I have messages from when the phone was off, or out of service range. Often I won't know till I randomly check days later, or when I miss a call (while on another call or in service range) and they leave a message.
5. Sound drops in and out from the other party. They can always hear me. Randomly, on some calls. I can have 3 good conversations, then the next I have to call back multiple times before I get enough up time.
5a. When I'm making a call, I may not even hear the outgoing ringing tone.
6. On any new call, the the volume on my Bluetooth headset is usually down about half way. I click the Vol+ and it immediately jumps to full, the volume bar already being at full.
7. When it rings, it often takes a second or more (after the ring tone has started) for the screen to turn on.
On suggestion by a friend, I disabled a lot of notifications, but the lock screen still won't unlock even when the only thing showing is the clock.
I guess there is problems with the the phone hardware, the ROM or incompatibilities with it and an APP.
Is there some diagnostics, or an app that I can run that will log what is going on and I can have someone look at those logs for me?
You should ask in Paranoid Support Thread
http://forum.xda-developers.com/xperia-zl/orig-development/rom-paranoid-android-5-t2992023
Thankyou. I could not find it.
edit: That thread is closed. There is a link at the end for a 'new home', but that thread is under Xperia ZL. Is the ZL considered the same phone?
I'm really sorry.
i gave you a wrong link. Shame on me.
http://forum.xda-developers.com/xperia-z/orig-development/rom-paranoid-android-5-t2976930
This is for yuga/c6603/"Xperia Z"
Since updating to marshmallow, my longer notification sounds, especially Calendar Snooze, are cut off.
I read somewhere about an app setting to allow it to turn the screen on as a fix. I did that but now I can't remember what app I made the change in or where I read that suggestion. I thought it might have been Light Flow, but I can't find it in there.
Now my power button fails to wake up the screen the majority of the time. Sometimes the lock screen will flash for a fraction of a second and go black again. Usually it takes 6-10 tries before the screen finally stays on so I can use my phone.
Since the wake up problem started when I tried to fix the notification sound, I'm pretty sure they're related. Any ideas?
Sent from my Nexus 6 using Tapatalk
JimSmith94 said:
Since updating to marshmallow, my longer notification sounds, especially Calendar Snooze, are cut off.
I read somewhere about an app setting to allow it to turn the screen on as a fix. I did that but now I can't remember what app I made the change in or where I read that suggestion. I thought it might have been Light Flow, but I can't find it in there.
Now my power button fails to wake up the screen the majority of the time. Sometimes the lock screen will flash for a fraction of a second and go black again. Usually it takes 6-10 tries before the screen finally stays on so I can use my phone.
Since the wake up problem started when I tried to fix the notification sound, I'm pretty sure they're related. Any ideas?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
if youre using lightflow id suggest wiping the data in it and resetting your notification settings. it does tend to override the system so i can see that screwing with the duration of the notification, and starting fresh usually solves most problems
i have mine set to wake the screen for SMS but not MMS. it creates similar problems with the screen
Thanks for the info. I tried just toggling the screen on settings on and back off for all of the Light Flow apps, and it seems to have fixed my screen turn on problem, at least for now.
Sent from my Nexus 6 using Tapatalk
I'm having the same notification sound cut short problem, I have a nexus 7 wifi 2013 model running Mohamed rom v2.1
Whenever anyone calls me on google hangouts, the ring only lasts for a second before its cut off, this doesn't happen if the front cover is open, it happens only when its closed.
I didn't have this problem on kitkat, but on MM this problem started from day 1.
I don't see any light flow option anywhere.
Any suggestions to fix this will be very appreciated.
Thanks.
A.Ahmed79 said:
I'm having the same notification sound cut short problem, I have a nexus 7 wifi 2013 model running Mohamed rom v2.1
Whenever anyone calls me on google hangouts, the ring only lasts for a second before its cut off, this doesn't happen if the front cover is open, it happens only when its closed.
I didn't have this problem on kitkat, but on MM this problem started from day 1.
I don't see any light flow option anywhere.
Any suggestions to fix this will be very appreciated.
Thanks.
Click to expand...
Click to collapse
LightFlow fixed my screen problems, but it was just a coincidence that I installed Marshmallow and my sounds got cut off around the same time. I'm still looking for a solution to that issue. Similar to you, if my screen is on, the notification sounds work correctly. If the screen is off, they get cut off.
I've had this problem with 2 different roms now (PureNexus, Chroma) on a few kernels (stock, ElementalX) so I'm not sure whats causing it but I need a fix. In a call, many times the screen just stops responding. Sometimes I can turn the screen on/off using power button and its fixed. Other times nothing works and I have to do a hard reboot by holding down power key since nothing else works on screen.
This is on latest version of the rom/kernels. Any ideas?
When you say its stops responding, do you mean it goes dark and nothing displays on screen? Or that its on with everything displaying but tapping it does nothing?
Only when in contact with ears?
akholicc said:
When you say its stops responding, do you mean it goes dark and nothing displays on screen? Or that its on with everything displaying but tapping it does nothing?
Click to expand...
Click to collapse
Its on, touch doesn't do anything. The phone is working since volume keys bring up the UI but you can't do anything. Also proximity sensor works, it turns on/off as I bring near ear. I don't have a screen protector.
ECrispy said:
Its on, touch doesn't do anything. The phone is working since volume keys bring up the UI but you can't do anything. Also proximity sensor works, it turns on/off as I bring near ear. I don't have a screen protector.
Click to expand...
Click to collapse
I'm having a similar issue from the last month.. I'm on DP5
when i get a call most times the screen is off.
To answer the call i've to put on the screen, unlock the phone and then go to the heads up notification and choose answer there..
waiting for nougat final hoping it'll fix this.
Tried fiddling around with notifications importance setting.. it helped a little but then there was the annoying heads up showing along with the regular incoming call screen.
Sometimes (very rarely, has happened twice) the screen just remains black and will only work normally after a reboot.
Anybody have any suggestions?
I was having similar issues, also on the Developer Preview and I ended up noticing that the phone app was blocked from showing any notifications despite the fact that I never set it that way. I would hear the call ringing but would never see the screen to answer. Just changed that setting and everything was back to normal. Perhaps something is causing the phone app to fail to show notifications for you as well.
So I bought this phone yesterday, stock and no third party app. did a factory reset inserted the simcard and recieved a sms. when screen was off, a green small notification was blinking on left upper part of screen (something like what third party apps like aodnotify do but it was better). I was amazed that samsung finally did something to fill the void of an actual notification Led. but after my second factory reset (after a 450 mb update) the feature was gone!!
I searched every where for it. tried different settings in Aod and edge light and... nothing
can anyone explain this to me? could it be an experimental feature on my stock firmware that was removed from latest update?
thanks in advance
I don't understand it either. I don't have it on screen off but I have it when I charge the phone or answer a call. Weird behavior.
That's being used as a proximity sensor I believe to turn the screen on and off during calls. It might also disable the screensaver/always on mode if the phone is face down.
thanks for the answers.
Edit: that's the proximity sensor as you said which lights up during calls, but I don't know why it was lighting up when there was no app running and the screen was off. odd behavior! perhaps accidental touch detection was acting incorrectly.