I use CM7. My dialer buttons are temporarily unusable or frozen while on a call. There may be a connection to the proximity sensor becaue it MAY only happen after I pull my face away from the device.
This problem comes up often, in the following circumstances:
1) I am trying to hang up (end a call) the end button doesn't work for several seconds
2) I am trying to use the touchtone keypad and can't switch to it for several seconds
3) I am trying to switch to speakerphone but the button doesn't respond for several seconds
Please advise
Sent from my HTC Vision using XDA App
I think this is a known bug.
My advice is to post in q&a section with questions. This area is for the pimps that create stuff(me not being one of them). I guess you could post question in general section as that seems to be the new q&a section
Cheers
Sent from my HTC Vision using xda premium
Yea, this is definitely a Q&A type question and should not be in the development thread.
Happens to me ALL the time...It was never fixed in CM7. Works Well in MIUI or SENSE roms though. It is always a bother to tap the End Call button 10 times to end a call...
Thread moved to proper forum.
Related
Hi,
I have just switched from a Pre3 webOS phone to a HTC One X.
Whilst I am a reasonably technical user I am very new to Android.
I like the One X, know a little about rooting but still have some questions over issues that would be solved on a webOS phone by the plethora of patches that are easily installed.
Two specific questions;
1) Is it possible for the phone to be made to switch between loudspeaker and normal phone speaker dependent on the proximity sensor, i.e. when held to face on phone speaker and when held away from face switch to loudspeaker ?
2) Can you disable the swipey thing that you swipe upwards when you hit the power button ?
I did try to look for answers on these first but if I missed them, sorry !
Thanks
rege0039 said:
Hi,
I have just switched from a Pre3 webOS phone to a HTC One X.
Whilst I am a reasonably technical user I am very new to Android.
I like the One X, know a little about rooting but still have some questions over issues that would be solved on a webOS phone by the plethora of patches that are easily installed.
Two specific questions;
1) Is it possible for the phone to be made to switch between loudspeaker and normal phone speaker dependent on the proximity sensor, i.e. when held to face on phone speaker and when held away from face switch to loudspeaker ?
2) Can you disable the swipey thing that you swipe upwards when you hit the power button ?
I did try to look for answers on these first but if I missed them, sorry !
Thanks
Click to expand...
Click to collapse
You can change lock screens with apps for example. Widgetlocker
Sent from my HTC One X using xda premium
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
So i have been reading here alot on the Q&A and seem to have found relevant posts/threads mentioning this issue..i don't exactly know if this is isolated or its from a faulty batch or its really a stupid feature of the One X..currently i am pissed so great on this phone..sorry to some who loved this phone but this phone is PITA for me..
here are the relevant threads i have gathered..and some people discussing the same issue i have..
thread 1
thread 2
thread 3
on those threads the issue of "Sensor still staying up even the call is already done" is imminent and in one case it is using VIBER that this issue arises..well on my issue i don't have anything installed on my Phone so i am just using my stock Call app(HTC one..)and when i make calls this issue just repeats is self..
to be more precise
-when i make a call, it will turn on sensor then it will immediately turn off screen even if the phone is not even near my ear..
-after the call the sensor is still lit up so i have to make a dummy call to turn it off and on this instance the screen again shuts itself off and sometimes its hard to wake it up..
if someone can provide a solution to this much better..or can explain to me what the heck is this phone made off..and what the heck this phone is doing..i have tried almost every kernel and reverted to stock via RUU still the same friggin issue persists..
Hi,
I'm having an issue with my Galaxy S3 and was wondering if anyone else has had a run in with this problem. My Galaxy S3 seems to auto answer phone calls when there is background noise. It has happened while at a restaurant, while in the car with music on, and from hearing a lawn blower outside.
I've searched and couldn't find any help or any fixes. I do not have S voice enabled at all, no motion shortcuts enabled, Home button not checked to answer phone calls, no bluetooth headset setting for auto answer, etc. I've tried factory resetting phone but that didn't fix it. I was able to get phone replaced within first 2 weeks for another one but exact same thing happened.
Anyone else ever hear about anyone experiencing this issue? It seems I can't find any thread other than one from googling about it for T-Mobile specifically.
Any help or advice would be appreciated. Thank you
I guess you have enable voice command from which you can answer and reject calls. Search in setting of ur phone.
Sent from my SGH-T999 using xda premium
Can you reproduce this problem yourself or is it completely random?
I'm assuming your running stock unrooted
Sent from my SGH-T999 using xda premium
Go to svoice settings click on control apps and another menu should show up make sure incoming calls is Unchecked... Most likely this is the problem.. I know you said svoice isn't enabled but at least check it out.. I was having this same problem..
Screen shots attached
Sent from my SGH-T999 using xda app-developers app
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Yeah, I never even had the S Voice activated on the first one. When I got my replacement I immediately tried that and turned S Voice on so I could uncheck everything. It would randomly happen when there is background noise. No one else I know with the SG3 is having this issue and I've had it on two phones.
I don't have any apps installed (don't even have a gmail account on either of the phones) and it is completely stock and updated to latest firmware.
Noticed on CM10.1 4.2.1 4.2.2 ROM's that when you call into voicemail or banking menu that requires you to press the dial pad to enter in menus options and account number info doesn't work.
I was able to fix it by turning dial tone touch sounds off in the dialer options. Just thought I'd let you all know in cause someone else is having this issue since a Google search brought up really vague results.
Hope I posted in the right place. Move if needed.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Actually, they work with the tones on. You just need to press and hold the keys a little longer to allow the other end to capture the tone.
BlackPhantomX said:
Actually, they work with the tones on. You just need to press and hold the keys a little longer to allow the other end to capture the tone.
Click to expand...
Click to collapse
That was the first thing I tried.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
I had same problem with liquidsmooth 2.1 RC2, and disabling touch sounds fixed the problem. However now that I upgraded to liquidsmooth 2.1 stable, the workaround does not work anymore. Neither does holding button, it's a set DTMF tone length. my voicemail is useless now. anyone have any idea on how to solve this problem?
UPDATE:
I did some more research, and the only thing I can think is the standard aosp phone.apk is used in both roms. I did find a feature request for it. (URL Below) So let me get this straight, my new phone cant dial a voicemail? or use a touch tone menu for calling tech support?
I would post this in developer forums, as there has been many questions lately about this problem, but I'm not allowed because I'm a noob. Guess I won't find a solution to this problem anytime soon. Seems I cant post links either......
***ttps://code.google.com/p/android/issues/detail?id=1428
Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
I don't have enough posts to post in the thread specific to this ROM.
Anyway, I just installed version 2.1 today and get the sleep of death every time the phone goes to sleep (both the timed sleep or me manually locking). The power button has no effect. Even holding it down does not do a force restart. I initially did a dirty flash thinking that was the problem. I did a clean flash and now am still getting the problem. Using the phone seems to be fine other than this issue... which isn't a small issue I can just overlook.
An incoming phone call is the only thing that I've seen wake it up.
Any ideas? Bad download?
I've had the same issue. Also my 3G wouldn't work on that ROM and I had the JB modem installed. I just want back to ol' faithful, CM10.1 some people are having an awesome experience with that ROM but I wasn't.
Sent from my SPH-D710 using Tapatalk 4
Sent from my SPH-D710 using Tapatalk 4 Beta
I love CM ... However, it has one huge flaw. I can't use the MHL out. I need to be able to use that.
Please read forum rules before posting
Questions and Help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
thinkbig12 said:
I don't have enough posts to post in the thread specific to this ROM.
Anyway, I just installed version 2.1 today and get the sleep of death every time the phone goes to sleep (both the timed sleep or me manually locking). The power button has no effect. Even holding it down does not do a force restart. I initially did a dirty flash thinking that was the problem. I did a clean flash and now am still getting the problem. Using the phone seems to be fine other than this issue... which isn't a small issue I can just overlook.
An incoming phone call is the only thing that I've seen wake it up.
Any ideas? Bad download?
Click to expand...
Click to collapse
Try to disable the ripple effect and see if that helps. Also check the md5 of the download to make sure it isn't a bad download; if you search the play store for md5 checker, it will make the process easier, but you could also use ES File explorer.