Hi, when someone tries to call me using Skype and im not able to answer it, the screen will stay on permanently!
Is there a way to disable this? Like with Tasker?
Am I the only one with this bugged Skype? The problem remains even after a full wipe and freshly installed ROM
Is this happening only with skype? What is your sleep time under settings->display?
OK Google fails on dialer and call Skype!
Related
About half the time, when I try to answer an incoming call, my Verizon TP2 will only mute the ring without answering the call. It responds the same whether I use the touch screen to answer or press the send key, and whether or not the phone is locked or unlocked when the call arrives. Has anyone had a similar problem or know of a fix? Thanks.
I got this behavior the first time I finished getting the phone set up how I wanted. I eventually had to hard reset to fix it.
I think it was probably s2u2 interfering with the nonstandard dialer / answer bits on the phone. Even uninstalling it didn't help though. I have not bothered to try reinstalling s2u2 after the reset though to see if it causes the problem again.
i have this same problem. as i recall there was some registry tweak you could do to fix it, but i cant remember it to save my life. I have the worst problem with being on the internet and trying to answer a call. anyone know of a fix? whenever i am on opera and try to answer an incoming call it just freezes and i have to exit opera and call the person back. anyone with a fix for this other than a hard reset?
i had the same problem before i flashed to 6.5 on my vzw tp2. I also suspected that it was because of s2u2: I followed to uninstalling and i kept on getting a message about s2u2.exe not being a valid app or something. I also thought it could have been because of the dialer i had. The dusk dialer...for sense2.1 while i had manilla. after the flash i reinstalled s2u2, and will see if this persists to happen again.
It happened to me for the first tiem twice yesterday, my phone awoke and I could see my taskbar icon switch to 1x but I didn't see a call then I got a voicemail, when I called the person back they said it rang 6 times and went to voicemail, and it happened again later where i saw the call box and slide to answer come up but the screen was stuck and I couldn't answer it, not even with the hardware key.
Same thing is happening to me. The first time someone calls it won't answer whether I use the soft key or the hard key and the screen just freezes. However when the person calls back, it answers immediately when I click the answer button. I don't have S2U2 or any other phone/lock apps which interfere with answering a call.
Same here guys, I have been having the same issue, but as I can see for weeks now I haven't been able to nail down a solution either...
I too have had the same issue for several weeks. More prevalent when the screen is locked. Rings once and goes to voicemail.
stupid double post.
I've only run across this issue when I am using too much RAM. Try using cleanram and closing out tasks that you are not using.
I have virtualized my RAM so that it never utilizes over 50 % available and have also made sure that all applications utilizing memory were closed down. The problem still persists and can not identify its cause.
reddington said:
I have virtualized my RAM so that it never utilizes over 50 % available and have also made sure that all applications utilizing memory were closed down. The problem still persists and can not identify its cause.
Click to expand...
Click to collapse
have you tried s2u2 and their call answering interface?
As title, any one encounter the issue? Sometimes cannot answer phone call since the phone freeze with lock screen. And also sometimes I cannot end call since the screen is freeze. Anyone encounter the same issue? Can share your comment here? Or Workaround? Thanks for any help
Same issue here, bezel and mainboard changed and the problem persists, can´t be bothered to send it back a third so i use the "No Lock" app, bad workaround but at least im sure i can answer calls now..
It only fails when it has been idle in my pocket for awhile and a call comes in.
Do You use custom ROM or Stock? Which version?
Do you have your phone underclock while its screen off? If yes, what CPU controller youre using?
Sent from my HTC Sensation 4G with Beats
I'm on stock and have the problem even after hardreset and no apps installed.
This is a common problem and no solution for it, i'm hoping on ICS.
I'm having this issue where the phone doesn't react properly to an incoming call (stock ROM, unrooted).
The phone rings, but the dialer screen with the controls to answer the call does not come up. It doesn't help if the screen is already on, I'm just staring at my home screen while it rings. There's also no call icon in the notification bar. When the caller hangs up, I immediately get a missed call notification.
Rebooting the phone solves the problem for a while, but then it comes back. I tried reverting to the stock dialer with no luck. I'm thinking of reverting to the stock launcher as well, but I'm not sure it has anything to do with it. Other than that I'm running out of ideas.
I've searched the web and it looks like people are experiencing all sorts of variations on this problem, but not the exact same thing, and in any case I haven't seen anyone post a tested workaround.
Has anyone encountered something like this and maybe knows of a solution?
Did you try clearing the data of the phone app in settings > apps?
If not, try that
Sent from my Nexus 5 using Tapatalk
I just install the factory image for lollipop. My screen doesn't turn on when I receive incoming calls. The ring tone will play but the screen remain turned off. I want the screen to turn on automatically with the incoming call dialer like kitkat or any other android version. so I can pick up the call. Any one else with this issue? How did you fix it?
idiopathic said:
I just install the factory image for lollipop. My screen doesn't turn on when I receive incoming calls. The ring tone will play but the screen remain turned off. I want the screen to turn on automatically with the incoming call dialer like kitkat or any other android version. so I can pick up the call. Any one else with this issue? How did you fix it?
Click to expand...
Click to collapse
I don't have this issue. maybe you had a bad install
I have the same problem on my N4, I installed the factory image two days ago, but just today I have this problem. When I turn on the screen, the call appears as a notification on the lockscreen, and I have to double tap it to answer it
I have the same issue. I installed the OTA. I had security certificates before which forced me to use a pin lock lock screen (My exchange account requires it). I installed a MOD to remove it so I thought that might be what was causing my problem. I removed the MOD by disabling the exchange APP but it didn't resolve it.
I have the same issue on about 50% of my incoming calls
Sent from my Nexus 7 using Tapatalk
I have this same issue. I even had it on the developers version. I also thought when you got text messages, emails, and other messages. You would get a black and white notification if you moved you hand over the phone. That doesn't work for me either. i have a Nexus 5 Build LRX21O. I installed it with the Nexus Root Toolkit.
I have the same issue on my Nexus 4 side loaded with Android 5.0 Lollipop. The screen won't turn on for any interactive incoming notifications like Phone Calls, Alarm calls..
It's an annoyance as you need to double tap the notification to answer, and the only way to go to speaker phone is to answer -> unlock -> Tap speaker
I checked around and my colleagues who use a Nexus 5 don't have this issue (OTA or Sideloaded). So I think this issue could be with a Nexus 4 build only (selectively that too). I am the only one who've posted this on reddit too.
/r/nexus4/comments/2mjoz7/screen_wont_turn_on_for_incoming_phone_calls/
I can also confirm this bug ... on Nexus 5 with LRX21O.
Same problem!
I have the same problem on my G3, but i didn't even installed Lollipop yet.
Same on my Nexus 5 with LRX21O.
I am having the same problem with my nexus 4, after a clean flash..
I unlocked the bootloader which triggered a full factory-reset and this issue went away on my Nexus 4 which is smoother than before.
I wanted to download a full ROM (since the issue was with OTA update), so was doing a bootloader unlock for the same. But i didn't even have to load up the full ROM as the issue went away.. :laugh:
jsgraphicart said:
I don't have this issue. maybe you had a bad install
Click to expand...
Click to collapse
after i updating my nexus 5 to android 5 during call screen doesn't auto turn off when i covered the screen sensor?
I noticed this too,not on all incoming calls, but on 1 out of 3 the screen stays black.
Do try a full factory-reset guys.. It solved my issue.. This update is really large and important to have such a major annoyance and work with that.. :angel:
gnanaswaroop said:
Do try a full factory-reset guys.. It solved my issue.. This update is really large and important to have such a major annoyance and work with that.. :angel:
Click to expand...
Click to collapse
I made a clean install (wiped everything) and the problem appeared.
I don't think it is a matter of dirty flash..
I also have this problem after installing from ZIP stock ROM (with format all things before).
Then I took a Google image and install it with ADB.
Now I don't have this problem.
screen doesn't turn off
My screen didn't turn off during phone calls with the developer preview and still doesn't with the official factory image from Google.
This is coming from a full flash via fastboot... Don't think this is a dirty flash issue.
Very annoying... No clue how this could be released.
It appears our problems are not related but I was able to fix mine
Nexus 5
OTA Flash
screen is blank for incoming calls and alarms, not periodic
I don't know which app specifically that was causing the problem but the problem went away after I uninstalled a bunch of apps. I am most suspect of a screen brightness app I was using to make the screen more dim than the default setting.
I have this weird issue since I've updated to OOS 10.01. When my phone is locked and I receive a phone call the screen flashes with the caller info for a second then goes back to the lock screen and then goes back to the caller info screen. This happens every time I receive a phone call when the phone is locked.
Any insights?
Thanks
Please help, any insights/suggestions?
This is driving me nuts
Thanks
Something causes this issue, I have not been able to pinpoint the cause. I tried stock and rooted OOS 10 but no difference. I experienced the problem with both setups. Does not happen after a fresh install, but after a while starts to happen all over again.
Anybody else experiencing the same problem ?
Thanks
OK just a short recap, haven't had the issue for a while now. Still trying to find the cause.
Things I did differently since the last full wipe:
- did not install viper4android
- did not enable call recording
- did not give "Auto Dark Mode" app write permissions via adb (this is the one I believe is the most likely candidate)