First off I want to point out that this bug seems to be related only to T-Mobile S6's. I haven't seen this behavior on any other S6 other than multiple T-Mobile S6's.
So I have my lock screen set to lock automatically within 2 minutes, and to not lock instantly with the power key, with fingerprint security. Normally, within those two minutes, on any other S6 if you receive a text, the phone will turn on and give you a new message notification on a lock screen set to "swipe" to unlock; no fingerprint needed.
However, on the T-Mobile S6, if you receive a text within that 2 minute window, the phone will unlock itself to whatever screen you had locked it on. The phone will completely bypass the lock screen from standby, and display a new message notification on whatever screen it was last on. This is incredibly frustrating as sometimes I respond to a text, put my phone in my pocket and sometimes ignore new messages. And if those messages get to me within 2 minutes, I often end up pocket dialing them if I chose to ignore my phone. While I know that seems like an odd and specific scenario, its pretty common for me at work, and is the reason why every other Samsung S6 defaults to a "swipe" type lock screen to prevent that from happening.
I work a a major electronics department store, in the mobile department. Although we do not offer T-Mobile phones, I personally have a T-Mobile S6. I have never seen an AT&T or VZW S6 do this.
Any other T-Mobile S6 users noticed this?
Related
I've noticed an apparent problem with the Flip-to-mute feature that I suspect rather a large amount of people must have run into..
On my device this feature works fine when the phone is non-PIN locked (ie. you are either using it or have been using it recently before the PIN lock has time to kick in, mine being set to 5 minutes), this can be differentiated by the fact the incoming call is intercepted by the HTC app (name and big picture of incoming caller, if available, along with the big red and green buttons). However if the device is PIN locked, differentiated by the fact it is the standard Windows Mobile "Incoming Call" pop-up which overlays the PIN unlock screen) then the flip-to-mute feature doesn't work, assumingly as it is part of the HTC app.
Would I not be right in thinking a large proportion of people will be using PIN locks, perhaps enforced by corporate policy etc, and thus this be a rather large oversight?
Or - better still! - anyone got a fix?
Thanks in advance.
I have the same issue, any fixes?
yeah this happens to me too (US Diamond) and was wondering if anyone found a fix
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 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.
I picked up a white 32gb s6 edge in my local Verizon store on Friday, and all was well. Today I noticed that the Edge Lighting feature no longer works. It's enabled in my settings and worked when I first obtained the phone. I tried restarting it to no avail. When I receive messages my screen lights up and shows the lock screen instead of showing the coordinated colours. This only happens when the screen is face down though, and the screen stays locked when it's face up and I receive a text. I tried turning the phone off and back on and switched the edge features from the right side to the left side and the first time I received a text the screen flashed on for a moment and then locked again and the edge lighting was turned on. It did not work after that, however, and I switch the features back to the right side. The screen no longer lights up when I receive a text when my phone is face down, and the lighting feature is still not working. Is there anything I can do?
I would get the device replaced.
Sent from my SM-G925V using XDA Free mobile app
onceuponanandroid said:
I picked up a white 32gb s6 edge in my local Verizon store on Friday, and all was well. Today I noticed that the Edge Lighting feature no longer works. It's enabled in my settings and worked when I first obtained the phone. I tried restarting it to no avail. When I receive messages my screen lights up and shows the lock screen instead of showing the coordinated colours. This only happens when the screen is face down though, and the screen stays locked when it's face up and I receive a text. I tried turning the phone off and back on and switched the edge features from the right side to the left side and the first time I received a text the screen flashed on for a moment and then locked again and the edge lighting was turned on. It did not work after that, however, and I switch the features back to the right side. The screen no longer lights up when I receive a text when my phone is face down, and the lighting feature is still not working. Is there anything I can do?
Click to expand...
Click to collapse
Are you using the people edge? I had the same issue and I was able to get it working again. It is not an accelerometer issue. I disabled the people edge as soon as I got the phone since I figured I would never use it. After a day or 2 of using the phone I realized the edge lighting was not working at all even though it was enabled. What I did was re-enable the people edge, set a friend to a color and then I had that person text me to see if that was working, which it did, so at that point I was sure it wasn't a broken accelerometer as some users have stated. I then deleted that friend from people edge, (so that all colors were set to default) I once again turned off the people edge and then finally retested the edge lighting and voila! It worked. It must have been some kind of glitch that I reset by re-enabling the people edge and then turning it back off. It has been 2 days and I can confirm it is still working. I hope this might work for you too! Let me know!
Some of y'all have probably gotten the latest update, that includes the Dec security patch, camera improvement and more importantly that new spam-screening stuff. Well, I've gotten 5 spam calls today, after not having one for days, and when the caller hangs up (after hearing nothing but silence from me) the screen locks up. But just the call phone app/call screen.
I can hit the home button and return to my home screen just find, close and reopen the phone app just fine, but that hangup freeze is kind of annoying. Reason being because after every spam call ends you know about that "block number" option that appears right after the call ends? I can't get to it because of this bug. I tried taking a screen shot but it wouldn't let me because the screen freezes.
It's not a big deal, just a minor inconvenience but I wanted to know if any other T-Mobile user with the latest OTA has experienced the same thing.
I'm on Verizon and have a similar problem. It's a major pita. Anytime I get a call my phone freezes up. I can't unlock it for at least a few tries, once unlocked all I've got is a frozen black screen with a missed call notification and an ongoing incoming call notification at the same time. Neither can be dismissed or cleared. It does show me the options to but they don't work when pressed. Average lockup of my phone is upwards of 5 minutes. If I miss a call no matter how long ago it came in I've got the same issue unlocking and it always displays the missed call and appears that the call is either active or incoming. Basically can't use the phone as a phone. Texts work fine however.