If I use one of the default ringtones, when someone rings they hear one and a half rings before my ringtone starts playing. If I use a custom mp3 ringtone then the person hears 3 rings before my ringtone is played!!!!! I tried using .wav files but they also gave a delay of one and a half rings.
In all cases the phone starts to flash and light up almost immediately within the first ring so its just the dialer and/or ringtone taking time to initialise.
I wanted to see if this is just me or if anyone else was having same problem since I've searched and previous android devices didn't have any problems.
Note: I had the exact same (if not similar) ring delay on my diamond but I fixed that by using wav files and the wm5 fix (it was also solved completely in custom roms). Is there a similar way to fix/minimise the delay on the hero?
In WinMo, there is a RegEdit to resolve this so you can change the delay.
Is there nothing in options? Like it might be set to vibrate first then ring?
I've just double checked the setting options but there is nothing about the order of ringing/vibration. I also killed touchflo using taskmanager (couldn't find another way to disable it) to see if it would make a difference but the delay was still the same.
I was going to try and transfer my ringtones to the phone memory itself...but the file manager just says 'couldn't be moved'.
Am I the only one with the delay?...if so it could be something I've installed then....
Any solution for this? I have the same behaviour on my hero. It flashes, then vibrates, then ringstone. Can this behaviour be modified? I want it to flash, vibrate and ringtone all at once from the very beginning.
Yeh I'm having the same issue aswell, there no way of setting the order.
sounds like it needs to load the resources before it can play the ring tone..
just like diamond1.. it lags when ppl call..
:/
I just tried my hero, no call lag at all.
NisseGurra said:
I just tried my hero, no call lag at all.
Click to expand...
Click to collapse
Hmmmm, is your hero branded? Also, what format are your ringtones in?
I doubt it, but could it be a network thing? I'm on Orange uk...what network is everyone else on?
Unbranded from handtec, use "old style" ringtone
NisseGurra said:
Unbranded from handtec, use "old style" ringtone
Click to expand...
Click to collapse
I only get the delay when I'm using custom ringtones.
i have a t-mobile g2 and there is a big delay in a person calling me before the screen wakes up and i can see who it is
the light on the scroll ball comes on, but the vibrate and ringing doesn't start until 3 rings on the caller's phone have passed
any help?! it's really annoying
Although I have noticed that the light goes off before the ringing and screen wakes up, what the person calling you hears is not reality.
It is somewhat network dependent, but when you call someone you often hear rings before the person you are calling actually hears them on their phone. This is because there is quite a few seconds of of network negotiation going on, and the telcos think it is better to give you an indication that it is connecting rather than nothing at all, so they often start the rings at the connecting stage.
ah! but sometimes when the phone is on my desk i can see the ball flashing for about 3 seconds (if not more) before the screen livens up and i can see who is calling
I have this problem too on a SIM free unit. Using custom mp3 ringtone for calls and a sound exported from a soundboard for my message tone.
For calls at first it just vibrates and the trackball flashes and then a few seconds later the screen will light up showing the caller and the ringtone will start.
Not a massive issue obviously but would be nice if it all happened at once as I would expect.
bigviv said:
ah! but sometimes when the phone is on my desk i can see the ball flashing for about 3 seconds (if not more) before the screen livens up and i can see who is calling
Click to expand...
Click to collapse
I have exactly the same issue, except its everytime rather than sometimes.
I am using a white unbranded Hero, and one of the standard ring tones.
Ringtone lag on my device is present too. But i guess that having used winmo after so long got myself immune to this.
It seems that the number of people with this problem is low otherwise this thread would be booming. I've reduced the delay to one ring by using wave files...but sometimes it still does produce a longer delay.
Note: I also get this problem with texts...the trackball lights up but the tone is heard after a couple of seconds. Hopefully the upcoming update will sort it out.
fl4r3 said:
It seems that the number of people with this problem is low otherwise this thread would be booming. I've reduced the delay to one ring by using wave files...but sometimes it still does produce a longer delay.
Note: I also get this problem with texts...the trackball lights up but the tone is heard after a couple of seconds. Hopefully the upcoming update will sort it out.
Click to expand...
Click to collapse
I don't think that the number of devices with this problem is low. On the contrary, i believe it is prominent on most of the devices but just that most of the people here have been using winmo for ages and are quite used to this "ringtone delay"
I for a fact considered it to be normal until i saw this post . I don't think htc updates will solve it up ( never did for diamond ) but i just hope that once chefs start cooking custom roms for our heroes, they'll figure out a tweak or something to reduce this delay.
Me too
I also have the issue of lagging ring/notification tones for call, text messages, and emails. Screen could also come on sooner for calls, although I find that unless I have the phone next to me on the desk, it's not an issue as by the time I get it out of my pocket or so, everything works as it should.
Just so people don't think the number of people affected by this is low. I think it's rather a case of most people not considering it much of a problem.
Yup, I have the problem. I could alter the registry on WinMo so it didn't happen, but seems to happen quite a bit on my Hero. I even get it sometimes when the phone rings for 1 second then goes silent.
Ring delay is annoying though
I've been searching and I'm trying to find out if there's a way to keep the screen from coming on with phone calls when I'm using my bluetooth. I'd like to be able to keep my phone in my pocket, but the screen gets pushed sometimes if I'm walking and hangs up on people and things like that. Since the BT lets me make calls and answer them without touching my phone, it just makes sense not to have the screen come on. (Same goes for SMS wakeup but I've found the fix for that)
I'm looking for an app that will lock the screen when the phone is upside down. Here's my problem. I keep my phone in my pocket, generally top shirt pocket. I'll be on a call using a headset (BT or wired) and another call comes in. The screen wakes up (in pocket detection doesn't make a difference) and because it is a press to answer button on the screen for call waiting, the phone connects to the waiting call 99% of the time.
So, I'm looking for a way to keep the screen from activating. In pocket detection would be good if it worked. Maybe just have the phone upside down in my pocket (not good for wired headset through). If there isn't an app, something like Tasker (looked but it doesn't seem like a solution) or anything else that might help is appreciated. I can't believe I'm the only one with this problem but it I don't see any complaints. TIA.
i too need a similar app
i use a bluetooth headset to receive call on my maxx. i have tried almost every app that detects in pocket using proximity sensor. they all work well. but the moment a call arrives or made the screen lights up causing all sorts of button press and the phone hangs. please suggest a app with which the screen should not come on whatever may be the event (call, message etc) when it is inside the pocket.
Try using:
Cheeky Hangup Guard
myLock Utilities
Angle offHookGuard
On Phone Touch Protection
I've not personally used them but their description sounds like it might be what you're looking for.
i use automagic automation to create a rule to lock or silence the phone when it's turned face down.
and yeah, i know it's a 10 months later reply
I have a specific problem that has persisted through multiple android devices, through all ROMs and builds.
Currently I am on a Verizon galaxy nexus with cyanogen 10.1 (background in case it's more relevant than I believe).
When a timer or alarm goes off on my device, or when I receive a call or text, my screen wakes automatically. I think this may be considered a "feature" in android. However, since my phone is nearly always in my pocket, it means that the screen turns on and often receives enough of a false signal in my pocket to disable an alarm or decline/accept a call. It is very inconvenient and would be alleviated if I could specify that I want my device to turn on the screen ONLY when I press the power button.
I know that others have the same problem from searches on xda and elsewhere, but I don't see solutions (except what looks like a registry hack on some specific devices)
Note: I am not looking for a suggestion to get a cover to stop screen interactions while in my pocket, nor do I want to hear about a more elaborate lock screen to keep said interactions from interfering with alarms/calls. The problem is simply that the screen comes on at all with seemingly no way to change the behavior.
Thanks for reading and (hopefully) for helping with this problem.
I'm not sure it does what you need but you might try IntelliCover: https://play.google.com/store/apps/details?id=com.dragonnis.intellicover2
I can't find on its description that function but I read someone solved with that.
good luck
no dice
I installed the recommended app (a neat app, by the way), but it doesn't fix the problem in question. Alarms and communications still wake the screen.
Thanks anyway.
Hi,
Did you manage to disable screen wakeup ?
Thanks
Has anyone figured out a solution to this? I'd really wish the screen would only turn on with the power button... Even when phone calls come in, I always have to CAREFULLY drag it out of my pocket so I don't accidentally hang up or answer.... This and a thousand other scenarios
Howdy,
I'm currently running CM10 superlite http://forum.xda-developers.com/showthread.php?t=2180695 I have installed the bluesleep fix, but on reading all the information about that, this problem seems separate anyway.
Every time there is an active call, my screen locks as though the prox sensor has been tripped, and the screen will not unlock by any means other than battery removal. This is only while the call is active. If, say, the other person ends the call, I can unlock the screen with the power button as normal. The phone is not sleeping, the screen(and seemingly all input methods) is simply being disabled during the call. I had a call open for 2 hours this weekend because neither of us hung up. I only found out 2 hours later when I took the phone out of my pocket and heard him talking to his wife. hah!
It happens instantly when a call is picked up. No delay, no proximity activation required. When making a call, it happens the very moment you press the "send/call" button. I am trying very hard to remember if this has been happening since I installed the ROM, but can't be positive. I just installed it about a week ago, and can't for the life of me remember if I accessed my voice-mail during that time, prior to today(when trying to delete a message became an issue), but I'm 90% I didn't, meaning this has likely been happening since the install.
I have tried manually increasing the min cpu speed, but, this fix seems to be for a sleep problem, which this doesn't seem to be. It had no effect. All other threads that describe similar problems are either about different ROMs, and/or appear to be about actual sleep mode issues.
I am very happy with this ROM(this issue aside), and have spent a considerable amount of time tweaking and installing things that I really do not feel like doing again. I'm not the type of person who enjoys flashing their phone every other day.
Thanks in advance.
*updated info*
It seems that either using a headset or plugging one in will prevent/fix this problem. It keeps the screen from locking when making a call, and will unlock it if you are already on a call with the screen locked and unresponsive rear/volume buttons. Technically I used headphones, not a headset, but I am guessing it's the same mechanism.
I have tried adjusting any setting related to headsets and screen locking that I can find within the call settings, and anywhere else I can find one that looks related. No luck. Only workaround is plugging in my headphones... which I don't always carry.