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.
Related
When my phone is in the holster, or when charging, it automatically comes out of standby mode every so often. I don't know why it keeps doing that, but it has done it so much that I had to turn on the Lock feature on so the buttons don't get accidently pushed when in my holster etc (very annoying). I spoke to a friend who said it might be a program running in the background that keeps making the phone come out of standby because it doesn't happen to his TP. But the running programs list only has Text, and Calendar always open so I doubt its those that's causing.
Any ideas on how to solve this really annoying issue? And does anyone else experience this?
Note: My carrier is Sprint and I have no custom ROM's)
G00gle26 said:
When my phone is in the holster, or when charging, it automatically comes out of standby mode every so often. I don't know why it keeps doing that, but it has done it so much that I had to turn on the Lock feature on so the buttons don't get accidently pushed when in my holster etc (very annoying). I spoke to a friend who said it might be a program running in the background that keeps making the phone come out of standby because it doesn't happen to his TP. But the running programs list only has Text, and Calendar always open so I doubt its those that's causing.
Any ideas on how to solve this really annoying issue? And does anyone else experience this?
Note: My carrier is Sprint and I have no custom ROM's)
Click to expand...
Click to collapse
You will find that the Lock feature isn't really going to be any help either because the sliding of the keyboard will a) Wake the phone up and b) Unlock it as well if it slides more.
You can make this registry edit to make it so the slide doesn't wake up the phone. Now, when you get a text message or email (I think) the phone will wake up but as long as you don't slide it more than about half an inch, the phone won't unlock.
You should be using the lock feature on your phone anyway. If you haven't figured it out yet, you can make the "Long End key press" lock the phone. It works very well to make locking the phone quick and easy. Then you can either use the push button method to unlock OR side the phone open to unlock.
mrrogers1 said:
You will find that the Lock feature isn't really going to be any help either because the sliding of the keyboard will a) Wake the phone up and b) Unlock it as well if it slides more.
You can make this registry edit to make it so the slide doesn't wake up the phone. Now, when you get a text message or email (I think) the phone will wake up but as long as you don't slide it more than about half an inch, the phone won't unlock.
You should be using the lock feature on your phone anyway. If you haven't figured it out yet, you can make the "Long End key press" lock the phone. It works very well to make locking the phone quick and easy. Then you can either use the push button method to unlock OR side the phone open to unlock.
Click to expand...
Click to collapse
I guess I didn't phrase it right...I mean when the phone is just sitting there and the keyboard is not opening at all because it is sitting on a desk charging, no text or e-mail message go in or out, bluetooth not connected, and no alarms, or events pop up the phone comes out of standby...same scenario in my belt holster.
True I should be using the lock feature but I like to set the timer to 5 or 10 minutes but sometimes it comes out of standby before then.
G00gle26 said:
I guess I didn't phrase it right...I mean when the phone is just sitting there and the keyboard is not opening at all because it is sitting on a desk charging, no text or e-mail message go in or out, bluetooth not connected, and no alarms, or events pop up the phone comes out of standby...same scenario in my belt holster.
True I should be using the lock feature but I like to set the timer to 5 or 10 minutes but sometimes it comes out of standby before then.
Click to expand...
Click to collapse
Interesting... You are really burning up your battery (if not plugged in) letting it not go into standby for 5-10 minutes but I wonder if it some other data transmission. What is your email interval set at? Even if no emails are received, it's still sending a data "pulse" to the server.
I have te same issue (Alltel Touch Pro)
I leave the phone on the charger overnite, and sitting by itself,
even with Lock on, it will wake up, stay up the timeout period,
then go back to sleep. Like it has Sleep Apnea?
I do email by webmail so that's not an issue.
mrrogers1 said:
Interesting... You are really burning up your battery (if not plugged in) letting it not go into standby for 5-10 minutes but I wonder if it some other data transmission. What is your email interval set at? Even if no emails are received, it's still sending a data "pulse" to the server.
Click to expand...
Click to collapse
fuzzynco said:
I leave the phone on the charger overnite, and sitting by itself, even with Lock on, it will wake up, stay up the timeout period, then go back to sleep. Like it has sleep apnea?
Click to expand...
Click to collapse
mrrogers: What I meant was I like the Lock on feature to come on after 5-10 minutes...it is already in standby mode, but the lock feature is not activated until 5-10 minutes (look inside your lock settings and you will see what I mean) so I am not draining the battery.....e-mail interval is set at 4 hours so it can't be that. Even if it was that, the screen should not wake up just for sending data in or out.
fuzzynco: YES I have the same problem...its as if the phone does not want to sleep. It stays up for the timeout period then goes back to sleep then turns on again a few minutes later for no apparent reason...but for me it also comes out of standby even when not being charged.
I suppose mine might do it too then, I guess I never notice because I plug in to charge and go to sleep. :-D
I am going to test this out tonight and see what my phone does. I am running a custom Rom so who knows what might happen. I thin something that also could mask the fact that this is happening to me is that my backlight and power setting are 30sec and 1min.
If I'm not doing something on my phone, it is locked. Unlocking is so simple I don't bother with timing the locking event. I think you must use the actual "Password" protection right? I do not use that feature but I know the settings you are referring to. I have only been referring to the device lock.
mrrogers1 said:
I suppose mine might do it too then, I guess I never notice because I plug in to charge and go to sleep. :-D
I am going to test this out tonight and see what my phone does. I am running a custom Rom so who knows what might happen. I thin something that also could mask the fact that this is happening to me is that my backlight and power setting are 30sec and 1min.
If I'm not doing something on my phone, it is locked. Unlocking is so simple I don't bother with timing the locking event. I think you must use the actual "Password" protection right? I do not use that feature but I know the settings you are referring to. I have only been referring to the device lock.
Click to expand...
Click to collapse
My backlight and power settings are the same as yours.
I didn't understand your last paragraph. All I have enabled is my "lock" feature in the settings. The system lock with password is enabled after 5 minutes, but that doesnt mean it takes 5 minutes to go into standby mode. Standby mode is seperate, and it only takes 30 sec to go to standby. But after 5 minutes of standby, the "lock" feature with password is enabled.
My problem is that before that 5 minute mark, the screen comes out of standby for no apparent reason.
I'll chime in here. Verizon Touch Pro. Haven't really done much to it, but a few advanced config settings. Mine will wake up in the holster, and even when it's just sitting there on the desk charging. I only let the screen stay on for a short time, so I haven't seen my battery suffer, but this happens enough to be annoying.
stanton said:
I'll chime in here. Verizon Touch Pro. Haven't really done much to it, but a few advanced config settings. Mine will wake up in the holster, and even when it's just sitting there on the desk charging. I only let the screen stay on for a short time, so I haven't seen my battery suffer, but this happens enough to be annoying.
Click to expand...
Click to collapse
exactly stanton! same thing with me...My screen is only set for a short time so I haven't seen battery loss but very annoying. Any theories out there?
Mine does it as well Sprint TP
I think all Windows mobile phones pretty much do this.
No idea why, but there's really nothing you can do about it.
I have been testing this evening and I can't get my phone to do it. I've been testing on battery power and will try plugged in tomorrow during the day.
Are you guys using TF3D? I'm not so I wonder if it might be something tied in there? Weather? Maybe some crazy update in the music tab?
Wish I could have helped... I'll check in tomorrow and report what I find on external power.
Long time lurker, here...
I seem to remember a similar issue with the XV6600 (Blue Angel) that was traced back to some settings having to do with the syncing with Exchange servers. My memory is kind of fuzzy on the issue, but that could be a place to start to look?
I've had my Vz TP for about a week now and have not had that issue.
Check Pocket Express. By default, it's set to update itself every 4 hours (at least on the Sprint TP).
My TP was doing the same thing (ie: coming out of Sleep on it's own). That, and the Data Connection wouldn't stay turned off. I don't like my computers and phones doing anything without my expressed permission so this was driving me nuts. Since I found the Pocket Express setting and set it to manual, my phone doesn't misbehave anymore.
Another setting you might want to look at is the QuickGPS settings. It will automatically try to update itself too. I changed mine to "Remind me when data expires" and "Auto download when connected to PC via ActiveSync" and that works best for me.
Basically, you have to go through every one of your apps and check their configurations. The two I mentioned above are definite sources of your problem but there could be others.
Pete
I havent had my VZW tp do that yet. But i see its doing it on all 3 CDMA companies. I wonder if its a glitch in the hardware or the data settings that makes it do that. I dont run any email through my phone. I wonder if the email is the cause of its insomnia.
I have the same issue whether on a stock or Custom ROM.
Not sure about effects on battery. Never really gaged it. I always get 24 to 36 hours before I have to recharge.
Its not a program in the background. I just created a clean ROM with nothing in it and it still does it.
deviantirish said:
I havent had my VZW tp do that yet. But i see its doing it on all 3 CDMA companies. I wonder if its a glitch in the hardware or the data settings that makes it do that. I dont run any email through my phone. I wonder if the email is the cause of its insomnia.
Click to expand...
Click to collapse
Im pretty sure its the HTC APM 1.5 drivers.
Any other thoughts?
I didnt see any problems with the TP waking up on any of the GSM versions.
I am curious as what would be different that would cause this.
My sprint pro also does this.
Ill have it in my hand and the screen will just turn on. Not sure why.
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
The past couple of days I've been noticing a couple of quirks with my phone and want to make sure that it's either not just me or some kinda bug in the UI.
The first one is with the speaker. In a couple of different games, when I click around, they'll play some sound. But sometimes, and I've only noticed this two separate times in the past week, the sound will interchange between really quiet and normal volume. I know this info doesn't really help much, but I don't know if it's a battery saving feature of the UI or what.
The more troubling issue regarding sound happened to me today. I was in the middle of a game and the sound just turned off completely. It wasn't muted and I clicked on the rocker to see if I had done so by accident, but nothing came out. I even checked with other games and by testing my ringtone. The only way I was able to remedy this was by restarting. I'm hoping these are purely software based and not my phone's speaker dying. :S
The second thing is less detrimental but weird. Two times today, while playing games, the lights on my dedicated button bar on the bottom would be off. I would exit the game, mess around on the home screen but nothing would bring them back aside from locking and unlocking the phone.
These are not complaints by any means, just a couple quirks I've recently come across that are hopefully universal in some form. Pardon my pickiness.
Ive been getting that sound issue also i was using navigation i basically restarted my phonealso
Sent from my ADR6400L using Tapatalk
Thanks for your confrimation on that one.
In case anyone is interested, I think I discovered the button bar lighting issue. I notice it being off today and not turning back on. I then realized that based on the ambient brightness, the light sensor on the top of the phone will either light up the bar or not. Pretty awesome way for it to save some battery.
I've had the sound issues as well. Not a deal breaker to me, but annoying. The issue with audio being low when recording video bothers me a lot tho.
Sent from my ADR6400L using XDA App
I had the sound issue when clicking when I was stock. It was intermittent and reboot would fix the issue. Haven't seen the others but usually play games on mute.
Discovered a couple more quirks over the course of the week. Would like to know of anyone else has experienced them.
I have the Facebook app (not the HTC Sense one) synced with my contacts. This way, I can fill in photos for the contacts I don't have photos for. But for some, I'd like to use the Gmail icon I made for them. I'll switch it in the linked settings, but after a while, it'll revert back to their Facebook icon. I'm assuming this is a bug with how the app syncs with my contacts?
The second thing is in the stock SMS app. Two times now, over the course of the week, I've clicked to open a particular thread and it instead opens up another one in my list that I didn't click on. I'm fairly sure this isn't user error as I've seen the thread that I want to open up highlight, but I could be crazy.
DJComet said:
The more troubling issue regarding sound happened to me today. I was in the middle of a game and the sound just turned off completely. It wasn't muted and I clicked on the rocker to see if I had done so by accident, but nothing came out. I even checked with other games and by testing my ringtone. The only way I was able to remedy this was by restarting. I'm hoping these are purely software based and not my phone's speaker dying. :S
Click to expand...
Click to collapse
I have had this happen as well. Something is amiss with sound.
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
How often did your watch return this error message? It happens several times a day for me. And of course it always happens the few times I really can't be using my phone. I'm about to just box it up and not use it. It causes me more grief than pleasure.
I should add that it's always eventually followed up by a Bluetooth disconnection. And my phone is always less than a foot away when it happens. Like in my car mount and I'm trying to set a quick reminder from my watch at a stop light or something.
Supposedly it cones from the battery saving feature on phones others claim its from switching from dalvik to ART...
Do you have any custom kernel or roms installed on your phone. I've noticed a lot of custom kernels change how much or often your phone sleeps or underclocks CPUs that would be active. This in my experience creates a delay in response.