guys i am having a problem. my sleeping Hero turns on screen after 2 rings. while hero is sleeping and a call comes it starts playing the ringtone and blinking the trackball but the screen still off. after 2 rings the screen turns on. any idea whats causing this??
stock or custom rom? i have mcr 3.0 and i dont have problems like this
Sustanon said:
stock or custom rom? i have mcr 3.0 and i dont have problems like this
Click to expand...
Click to collapse
i have mcr3.0, sometimes it rings immediately, sometimes not. it is obviously a problem with the phone (not the network or something): when i use xbmc remote for my mediacenter it will show the caller on my tv immediately, but it takes a few seconds for the phone to ring.
I read that if the file that you set for your ringtone is .ogg then it will appear immediately, but if it was mp3 then it would be delayed?
Related
Anyone getting a strange clicking sound coming out of the speaker? It always happens when my screen goes to sleep (around 1-2 seconds after) as well as performing some actions on screen.
Yep, I get this on GBRemix 2.1 whenever I start some action that involves sounds. I think it's just the speaker turning on and off. A little annoying, but I can live with it.
Strange part is it also happens when my phone is on silent. I agree it is annoying but I can live with it as well. Just wanted to know if I'm alone in it and if anyone had a fix.
Also noticed this using GingerTh3ory 4.2. Maybe a kernel issue?
I'm using Dream kernel
I am a new android owner. When I make a phone call the proximity sensor turns the screen off... great, no accidental screen pressing. However, when I finish the phone call or take the phone away from my ear... I get the lock screen. Why? Why doesn't the screen just go back on to whatever screen was on before the phone call... like the dial pad.
I find this annoying. To hang up a phone call, I have to unlock the screen first.
What phone are you using? Software version etc and are you rooted? This doesn't happen to me so it's not a general android issue.
Sent from my Galaxy Nexus
I have the Moto Droid X. Running CyanogenMod 7.1. Also using exDialer as a dialer replacement.
Does it happen with the stock dialer? If not that's your answer
Sent from my Galaxy Nexus
RTContent said:
Does it happen with the stock dialer? If not that's your answer
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Yep it happened with the stock dialer on ICS and it is happening with JB as well. I am really surprised it doesn't bother more people. What is most annoying is that, I initiated a new call and put my phone to my ear to only that the call did not even establish (e.g., due to network iss ue) and when I want to place the call again, it is already locked. It is definitely due to the proximity sensor, as the same thing doesn't happen if i never put the phone to my ear and just keep watching the screen to confirm that the call did get established (and started ringing).
njmsmith said:
I am a new android owner. When I make a phone call the proximity sensor turns the screen off... great, no accidental screen pressing. However, when I finish the phone call or take the phone away from my ear... I get the lock screen. Why? Why doesn't the screen just go back on to whatever screen was on before the phone call... like the dial pad.
I find this annoying. To hang up a phone call, I have to unlock the screen first.
Click to expand...
Click to collapse
If you are rooted, disable your Proximity Sensor in a call. To do so, add following line to /system/build.prop file:
Code:
gsm.proximity.enable=false
.
Plus, make sure to make screen timeout period long. You can use Widgetsoid app (or, other toggle apps) to make it infinite.
SachinShekhar said:
If you are rooted, disable your Proximity Sensor in a call. To do so, add following line to /system/build.prop file:
Code:
gsm.proximity.enable=false
.
Plus, make sure to make screen timeout period long. You can use Widgetsoid app (or, other toggle apps) to make it infinite.
Click to expand...
Click to collapse
I have display timeout set to 2 minutes, so that can't be the problem, as the whole experience when the call is not connected only takes 10 or 15 seconds to complete. However I have security setting to lock the screen in 5 seconds after the display goes to sleep. Perhaps that is somehow related, so I just increased it to 30 seconds, I will see if the problem goes away.
it happened a couple times....
i lock my screen with knock mode, but sometimes when i press the power button to see the hour, there is no knock mode and i can unlock the screen by drag!!!
also sometimes the sound (for sms or alarm) changes opposite and the sound for sms is the alarm sound...
thats all i have to say at this time... multitasking goes very well and battery too...
v20c-op1-hq software version
happened this to anyone?
I havent any problem like that. Just screen turn on when sms comes and my app social media just stopped when im not using my phone. Maybe, reflash the rom can make it normal
confirmed i have the 'no lock' problem sometimes too
Not always but at random times when I receive a text or a call the screen would stay black and wouldn't allow me to receive the call etc. The rings would keep going but the screen stays black. I am using Cyanogenmod latest nightly and AGNi kernel. Is there any way to fix this?
But if I give some time, the screen is back up. Happens during and after calls too. It's not a regular thing but it would happen randomly once a day or so.
It sounds as though the screen sensor isn't detecting the call. I know this is a common issue in a few lollipop based roms. One reason I personally haven't stayed on an LP rom. I believe that you can change certain settings in the build.prop file but as to what they are exactly I'm not familiar. You would need to search a few sites to confirm.
My screen dims rather quickly with the dialer on and then turns off. My default screentime out is 2 mins, but this doesn't apply to the dialer. It gets really annoying if you have to get through a couple of prompts and the screen keeps dimming. Any suggestions on how to address this? Either have the same 2 minute delay apply to the dialer, or even not have it turn off at all.
Thanks!
deroth said:
My screen dims rather quickly with the dialer on and then turns off. My default screentime out is 2 mins, but this doesn't apply to the dialer. It gets really annoying if you have to get through a couple of prompts and the screen keeps dimming. Any suggestions on how to address this? Either have the same 2 minute delay apply to the dialer, or even not have it turn off at all.
Thanks!
Click to expand...
Click to collapse
When I have Waze navigation on, my screen doesn't dim. When I make a phone call, I go back to Waze map screen. I can drag the phone call thingy wherever I want. If I need to mute, unmute I just click that to go back to call dialer interface for a few seconds. Then I go back to Waze screen to keep display on.
Yes, it's a wonky workaround, but it works. When I use this while driving, I make sure my phone is plugged in for charging -- because the display will stay on for the entire duration of the phone call.
ChazzMatt said:
When I have Waze navigation on, my screen doesn't dim. When I make a phone call, I go back to Waze map screen. I can drag the phone call thingy wherever I want. If I need to mute, unmute I just click that to go back to call dialer interface for a few seconds. Then I go back to Waze screen to keep b display on.
Yes, it's a wonky workaround, but it works. When I use this while driving, I make sure my phone is plugged in for charging.
Click to expand...
Click to collapse
Thanks for the suggestion. I'm surprised there isn't a better way to address this..