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.
Related
i have the pattern lock on, my question is if someone calls and i answer, once i hang up the screen auto locks again, is there a way to disable this?
chnky18 said:
i have the pattern lock on, my question is if someone calls and i answer, once i hang up the screen auto locks again, is there a way to disable this?
Click to expand...
Click to collapse
that defeats the purpose of the lock. the lock is to keep everyone that doesn't know the pattern out of your phone. if someone did get a hold of your phone and a call came then all they would need to do is answer the call hang up and use the phone freely.
I believe, the scenario is this:
Even when the phone is not locked before a call, and regardless of whether the call is originated or answered, when you hang up the phone using the red button, it locks the screen. That means if I want to make 2 calls in a row, I must unlock the phone after each call is over.
This does not happen 100% of the time - I have seen a couple of cases when I hang up and the screen does not lock, but I have not been able to figure out how it decides whether to lock the screen or not when I hang up on a call. In my opinion, the screen should never be locked by hanging up on a call, unless it was locked when the call was answered.
This is one of the more irritating behaviors of the phone - I hope for a change to make the red button function be sensitive to the call state and not lock the phone when it is used to hang up.
SirGe said:
I believe, the scenario is this:
Even when the phone is not locked before a call, and regardless of whether the call is originated or answered, when you hang up the phone using the red button, it locks the screen. That means if I want to make 2 calls in a row, I must unlock the phone after each call is over.
This does not happen 100% of the time - I have seen a couple of cases when I hang up and the screen does not lock, but I have not been able to figure out how it decides whether to lock the screen or not when I hang up on a call. In my opinion, the screen should never be locked by hanging up on a call, unless it was locked when the call was answered.
This is one of the more irritating behaviors of the phone - I hope for a change to make the red button function be sensitive to the call state and not lock the phone when it is used to hang up.
Click to expand...
Click to collapse
Maybe the other party hung up before you pressed the "end call" button. This may cause the G1 to think you are locking the screen instead of trying to end the call. Try not pressing the end call button and just wait for the other party to disconnect the call. Not sure if it will work....its just a theory that I am too lazy to test..
SirGe said:
I believe, the scenario is this:
Even when the phone is not locked before a call, and regardless of whether the call is originated or answered, when you hang up the phone using the red button, it locks the screen. That means if I want to make 2 calls in a row, I must unlock the phone after each call is over.
This does not happen 100% of the time - I have seen a couple of cases when I hang up and the screen does not lock, but I have not been able to figure out how it decides whether to lock the screen or not when I hang up on a call. In my opinion, the screen should never be locked by hanging up on a call, unless it was locked when the call was answered.
This is one of the more irritating behaviors of the phone - I hope for a change to make the red button function be sensitive to the call state and not lock the phone when it is used to hang up.
Click to expand...
Click to collapse
this is the exact behavior i was describing and i too get the mixed results, sometimes it locks and sometimes it doesnt. i guess i will have to test out the theory of not eating end call and letting the other caller end the call.
Hi guys
I have noticed something weird. My phone won't ring when the screen is locked, in fact, it doesn't show the incoming call screen or anything. Eventually, I am told that "the cell phone I am trying to ring is either turned of or outside the cell phone network" by a pre-recorded message. I am running 2.1 black Quarx.
Its very strange, if the phone is unlocked and I ring it then it rings and everything is fine. If I ring it while its locked, then unlock it, then sometimes after 10 seconds it might ring eventually.
Has anybody got any idea about what is going on?
Actually, its a little more complicated as I have found out while been playing around a bit today. If I leave it for say more than 10 minutes, it won't ring. If I leave it alone for 10 minutes, then ring and let the phone ring for a minute my cell won't ring. If I hit the home button which wakes the screen up, the phone will - after a 2 or 3 seconds delay - show the incoming call screen and start ringing! It doesn't seem to matter if its plugged in or not, in fact, I can run "adb catlog" while ringing! Nothing in the logs seem to hiont at what the issue is.
I used to get something similar to what you are experiencing but somehow along the way the problems just stopped. I think its because I've flashed my phone so many times. Just reflash your phone and see if that helps. If it doesn't then flash to a different 2.1 version
Sent from my GT540 using XDA App
http colon slash slash dub dub dub dot stuff dot co dot nz/business/industries/4327808/Vodafone-customers-miss-calls-after-mystery-3G-fault
It is probably an issue with my cell phone network, rather than my phone! Which is good and bad, because it means I have to wait for those dicks to fix their stuff - I can't fix it myself.
Not even really sure what happened, but I was on a call, received another, and hit the answer button. When I looked at the phone again, there was just a normal call screen with something generic like "caller" on it, not the screen that shows both calls, and which one's on hold. So I had to hit the menu button in the bottom right to switch back. Anyone have this happen, or is it normal for the ONE? It may have been the first call waiting I've had, but I'm not even sure, am just so used to how the evo screen looked, I never thought anything about it.
So I just placed two calls in the last hour and both times, the screen locked and I was unable to hang up when I got to the person's voicemail because the screen wouldn't turn back on when I pulled it away from my face. I eventually got the screen on with the power button after a LONG delay. I checked dialer settings and regular settings to see if there was an option to keep the screen on when placing a call but didn't see one. I was rooted, but gave it up and went back to stock and installed the OTA 4.4 without issue. Anyone else experience this?
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"