I have been searching and have not found my particular issue yet. From time to time my phone will start making a popping sound and after it stops all audio is routed through the ear piece instead of the speaker. This has happened about 3 times so far and only started after NoDo. They only way I can make it stop is to restart the phone. I would appreciate any information you could give me.
memay118 said:
I have been searching and have not found my particular issue yet. From time to time my phone will start making a popping sound and after it stops all audio is routed through the ear piece instead of the speaker. This has happened about 3 times so far and only started after NoDo. They only way I can make it stop is to restart the phone. I would appreciate any information you could give me.
Click to expand...
Click to collapse
go in to diagnosis mode
1) open up dial pad and dial ##634#
2)find the diagnosis iconlisted in your app list (black gear icon/says Diagnosis)
3)dial in *#0002*28345# if not work then try *#0002*28346#
4)Click Get under the Device Gain (max/min) should be 1200 -500
5)keep the 7 in the first box
6)in the second box type in 1600
7)in the third box put 5
8)click set
9)click start
10)after start is not highlighted white, click the home buttom/windows button
11)after restart repeat steps to get back to the sound menu and click get to see if the phone accepted the new values.
this does modify the sound and makes it louder but it also resets it.
machspeed said:
go in to diagnosis mode
1) open up dial pad and dial ##634#
2)find the diagnosis iconlisted in your app list (black gear icon/says Diagnosis)
3)dial in *#0002*28345# if not work then try *#0002*28346#
4)Click Get under the Device Gain (max/min) should be 1200 -500
5)keep the 7 in the first box
6)in the second box type in 1600
7)in the third box put 5
8)click set
9)click start
10)after start is not highlighted white, click the home buttom/windows button
11)after restart repeat steps to get back to the sound menu and click get to see if the phone accepted the new values.
this does modify the sound and makes it louder but it also resets it.
Click to expand...
Click to collapse
Did you even read the question?
I haven't seen that issue anywhere, and even though you've noticed it after the NoDo update, I think that's more of a coincidence because it sounds hardware related. Check out the jack and make sure there's nothing foreign hanging around, otherwise, take it back under warranty.
thanatossassin said:
Did you even read the question?
Click to expand...
Click to collapse
You just posed the first question in the tread, actually.
Related
Hello
My tytn require a quite large amount of time to wake up and I was wondering if I was the only one in this case.
It may require from 2 to 4 seconds to recover from standby; I tried to phone myself and it took about one or 2 "tuuuut" (sorry, no better english translation for that word =)) before the phone began to ring; this is quite anoying because I have to answer very fast in order not to miss call.
The virtual keyboard used for inputing the code is also getting on my nerv; most of the time it start with the landscape layout (without any reason) and it take 2 sec to adjust to the portrait layout; during that time it is hard for me to input my code correctly because the size of the key is changing.
So, 2-4 seconds for waking up plus 2 seconds for keyboard adjustement is in my opinion quite slow. Am I the only one experiencing this? Are there fixes out there?
I also have some trouble with notification; it wake the device up! If the device is not password protected (only after 15 minutes on my phone) it start most of the time PIE (because of the hardware button). All this lead so to my second question: Is there a way not to wake up the device (at least the input) in order to avoid unwanted press on the hardwares buttons.
Thank you in advance !
fun_key said:
Is there a way not to wake up the device (at least the input) in order to avoid unwanted press on the hardwares buttons.
Click to expand...
Click to collapse
Settings -> System -> Key Lock -> When device is off: "Lock all buttons except Power button"
Thanks for your fast answer, i ll give a try!
Concerning the screen orientation issue I found out that it is related to the HTC case magnet.
EDIT:
In fact it was already configured like this; the device is not waked up by the hardware buttons, but by the notifications.
if you use the key lock you can avoid unwanted key presses. As for wake up times. I don't think anyone who has this device wants to admit that it takes to long cause they paid sooo much for it. However, I will admit that it does take a long time to wake up. I am comfortable saying this because its much like a turbo car, at first its not as fast as most naturally aspirated cars (turbo lag), then it blows their doors off. So it takes a couple seconds to wake up, then its faster then most other devices.
Later, Lew
Agreed. Coming from standby I get two rings of the "Old Phone" ringtone before it goes to voice mail.
I am hoping that new firmware will resolve this issue - my wizard was certainly more responsive when i presses the poer button to bring it out of standby. This is furthur delayed by the fact that i keep scabbling around the top of the device for the power button insted of the side!
pof said:
Settings -> System -> Key Lock -> When device is off: "Lock all buttons except Power button"
Click to expand...
Click to collapse
This doesn't help with the particular problem. What I think fun_key is trying to say is that whenever he gets a notification (for example when he gets a new sms message or a notification for a meeting) the phone will come out of sleep mode, so the key lock setting for "when device is off" won't be in effect. Instead the device will be powered up and accepting all keypresses, like the IE / Messaging- buttons, not to mention any presses on the screen.
I too find this annoying, and wish there was a way to make the phone go back to sleep after showing me a notification, instead of waiting for the default sleep time to go by. There are programs out there that have this functionality (for example MortSaver) though, so my advice would be to use those.
- Pud.0
thank for the mortsaver ip; i ll give a try!
Have exactly the same problems as fun_key (power button, keyboard in landscape, etc), and I suspect most of other people do. The wizard was definitely more responsive.
fun_key said:
It may require from 2 to 4 seconds to recover from standby; I tried to phone myself and it took about one or 2 "tuuuut" (sorry, no better english translation for that word =)) before the phone began to ring; this is quite anoying because I have to answer very fast in order not to miss call.QUOTE]
I've found a solution to the problem regarding the length of time before a call is missed (this is probably known by most people, I only found it after tinkering with the settings):
Start>Settings>Phone>Services(Tab). Choose Call Forwarding in the list, then click Get Settings. Change the 'Forward After' setting to a higher number. I changed mine to 25 seconds. Problem solved for me!
Click to expand...
Click to collapse
g00nerz said:
fun_key said:
It may require from 2 to 4 seconds to recover from standby; I tried to phone myself and it took about one or 2 "tuuuut" (sorry, no better english translation for that word =)) before the phone began to ring; this is quite anoying because I have to answer very fast in order not to miss call.QUOTE]
I've found a solution to the problem regarding the length of time before a call is missed (this is probably known by most people, I only found it after tinkering with the settings):
Start>Settings>Phone>Services(Tab). Choose Call Forwarding in the list, then click Get Settings. Change the 'Forward After' setting to a higher number. I changed mine to 25 seconds. Problem solved for me!
Click to expand...
Click to collapse
Glad your problem is solved. Perhaps others may find the following of note as well as your solution above:
http://forum.xda-developers.com/archive/index.php/t-258109.html
Mike
Click to expand...
Click to collapse
Hi team
I have the same issue, every time i turn my hermes on after its been off for more than say 30seconds it starts in landscape mode then switches to portraite mode, its driving me mad, at least i now know i am not the only person. maybe this will be fixed in the next rom update, fingers crossed aye
UPDATE: i also found this thread
http://forum.xda-developers.com/showthread.php?t=286552&highlight=standby+landscape
does anyone have any thoughts on his comments?
I actually think that the reply in the thread i posted above is correct,
My Hermes is an IMATE JASJAM (same thing of course) and i use the original belt holder that came with it, it has two (2) magnets in it to keep the cover shut, when ever i get a msg and i pull it out of the case (turns on automatically to show me the msg) its always comes out in landscape mode.
I turned my phone on and passed the cover with magnet side down over the phone and sure enough as i did that the screen changed from portrait to landscape mode, thus confirming its the magnet that causes it and not a defect with the phone.
Anyone know how to change the in-call screen timeout? I think it's like 5 seconds right now. Maybe like 10 or 15 seconds would be a little more practical.
daveknights said:
Anyone know how to change the in-call screen timeout? I think it's like 5 seconds right now. Maybe like 10 or 15 seconds would be a little more practical.
Click to expand...
Click to collapse
Not sure but it times out so you can put it up to your face while your talking on it without the touch screen freaking out on us so i sincerely doubt there is any way to change it.
stats555 said:
Not sure but it times out so you can put it up to your face while your talking on it without the touch screen freaking out on us so i sincerely doubt there is any way to change it.
Click to expand...
Click to collapse
yeah but trying to navigate voicemail is a PITA... I did find the button that keeps the thing "live/on" while plugged into power... that at least is nice.
--M
daveknights said:
Anyone know how to change the in-call screen timeout? I think it's like 5 seconds right now. Maybe like 10 or 15 seconds would be a little more practical.
Click to expand...
Click to collapse
I'm not having this problem at all so I wasn't sure what people were referring to. However, I discovered that my sister was having the same problem described here and on other forums. Her phone would timeout within a second or two and it was extremely annoying to her. So off I went trying to help her.
Short Answer: Reboot the phone via the red/power key.
Long Answer: After several hours of troubleshooting with no luck I had her reboot the phone by holding down the red key and choosing to "Power off". Then hold the red key again to turn on the phone. After that it seems the problem went away. I've had her do other things but I'm not sure it was relavent so I'll stop here and see if this helps anyone else.
Huh? This is not a bug that you can simply do away with. The phone is supposed to time out.
On the other hand, I would like the option to adjust the timeout
Screen Backlight Timeout during a call
Is there a way to adjust the screen backlight timeout during a phone call? My timeout is set for 2 minutes, but during a call the screen shuts off so fast it does not let me dial extensions etc, and then pressing menu to light up, then menu to unlock then menu to bring up the keyboard, its kind of annoying. I just measured the time, its about 10 seconds.
This question is NOT ABOUT: Screen/Setting/Sound&Display/ScreenTimeout (that one has its own issues too, but this thread is specific to one issue)
Lol I have the same prob when I do phone banking. By the time I've pressed menu
Then flicked the dial buttons back up iam to late to press the button and have to start
Over again. Its really pissing me off now lol.
Adam
Amen... hopefully one of the developers can make this adjustable
Yes, it's one of my main gripes about the phone function.
They really should have made it adjustable independently of the standard timeout time. Because even voicemail prompts are a pain in the rear.
Power Manager
You can pick up the Power Manager application off of the Andoird marketplace. It allows you to modify the amount of time the screen is on during a phone call.
b2amedina said:
You can pick up the Power Manager application off of the Andoird marketplace. It allows you to modify the amount of time the screen is on during a phone call.
Click to expand...
Click to collapse
Really? Must be the new version I don't have. I have the first version and it lacks that function.
Thanks for the tip.
I know this thread is a bit old, but I'm having this problem and its really annoying!
I have the touch pro, and the display timeout while talking is like 5 seconds, and then I have to press that top button to get the screen to come back on, and I have to press it like 3 times till it comes back up. Really annoying when I'm pressing numbers with an automated system like voicemail.
Download power manager from the app store. allows you to change in-call time out and a truck load of other things.
If you want to find it on the net here - http://www.cyrket.com/asset/-5688572614148254173
That was driving me crazy - I changed mine to 30 seconds for in call.
Mods, please merge these two threads:
http://forum.xda-developers.com/showthread.php?t=458981
http://forum.xda-developers.com/showthread.php?t=439369
when a call comes in, i either push answer on the screen or hit the green button. however, it takes a few seconds before the my phone actually picks up the call. has anyone else run into this problem?
i just tried calling myself and the phone just keeps ringing the extra ~3 seconds before the phone picks up.
Here's an article on how to fix that, but it involves a registry editor and adjusting a setting
http://www.wmexperts.com/wm-cdma-phones-have-delay-when-answering-call-data-connection-read
I actually have this problem but the registry fix isn't what's wrong ...is there any other ideas?
i'm pretty sure it has to do with WM - I have a coworker with the Mogul and he says he has the same delay that i have both with answering calls and hanging up calls.
mjchoi824 said:
when a call comes in, i either push answer on the screen or hit the green button. however, it takes a few seconds before the my phone actually picks up the call. has anyone else run into this problem?
i just tried calling myself and the phone just keeps ringing the extra ~3 seconds before the phone picks up.
Click to expand...
Click to collapse
Try this one
It is not a fix per say for what you wnat but it will make your phone ring soner.
Get into your msl settings by pressing ##778# on stock rom (you will need your unlock code) and then click on edit, then click your left soft key (should be view info) then go to modem settings and change the slot cycle index to 1. What this will do is make your cell phone check the tower for incomming calls every 1-2 seconds instead of every 5-7 seconds.
thermus said:
Try this one
It is not a fix per say for what you wnat but it will make your phone ring soner.
Get into your msl settings by pressing ##778# on stock rom (you will need your unlock code) and then click on edit, then click your left soft key (should be view info) then go to modem settings and change the slot cycle index to 1. What this will do is make your cell phone check the tower for incomming calls every 1-2 seconds instead of every 5-7 seconds.
Click to expand...
Click to collapse
I agree that this works. It helped my pickups be a little quicker and more consistent. If you don't know your unlock code, google for an app called "getspc"
So i have been having a lot of freezes with using the phone function. Most of them happens:
1) when the phone rings, i try to answer it using the slider and it freezes
2) when trying to make a call, it gives me the connected vibration and the call timer starts to count, but no voice come through. I will have to hang up and it freezes then.
Does anyone have the same issue or any suggested solutions?
tonysosw said:
So i have been having a lot of freezes with using the phone function. Most of them happens:
1) when the phone rings, i try to answer it using the slider and it freezes
2) when trying to make a call, it gives me the connected vibration and the call timer starts to count, but no voice come through. I will have to hang up and it freezes then.
Does anyone have the same issue or any suggested solutions?
Click to expand...
Click to collapse
try hard resetting your phone.
shak7i said:
try hard resetting your phone.
Click to expand...
Click to collapse
i have, also tried different roms/radios. None solved the issue.
tonysosw said:
1) when the phone rings, i try to answer it using the slider and it freezes
?
Click to expand...
Click to collapse
Disable the below setting.
Start > Settings > Menu > All Settings > Today > Items
The setting "Today timeout", at the bottom left hand corner, should not be selected/checked/ticked/enabled.
I just installed Google Voice on my Epic 4G and received my first phone call on it - and was unable to answer. Two problems - first, when I answered, the greeting telling me to press "1" to accept was cut off at the beginning (all I heard was '...all from [spoken voice]. Press 1 to accept".
I can get past that, but then when I pulled up the dial pad to press 1, I was unable to. I pounded on the "1," was sure it was showing up, but it would not answer the call. I tried enabling audible touch tones but that didn't work, and I don't think there's a setting on the epic to change between long/short touch tones.
Does anyone know what's going on with this?
pissinguoff247 said:
I just installed Google Voice on my Epic 4G and received my first phone call on it - and was unable to answer. Two problems - first, when I answered, the greeting telling me to press "1" to accept was cut off at the beginning (all I heard was '...all from [spoken voice]. Press 1 to accept".
I can get past that, but then when I pulled up the dial pad to press 1, I was unable to. I pounded on the "1," was sure it was showing up, but it would not answer the call. I tried enabling audible touch tones but that didn't work, and I don't think there's a setting on the epic to change between long/short touch tones.
Does anyone know what's going on with this?
Click to expand...
Click to collapse
I think the second problem is a bug. It's not related to google voice but the phone itself. The dialpad is not very responsive when you take the phone off your face and the screen is back on. Wait a few seconds, and it'll be back again.
It happened all the time when I called any customer service number and tried to use the dialpad to choose in the menu.
Bigger problem
fookxixi said:
I think the second problem is a bug. It's not related to google voice but the phone itself. The dialpad is not very responsive when you take the phone off your face and the screen is back on. Wait a few seconds, and it'll be back again.
It happened all the time when I called any customer service number and tried to use the dialpad to choose in the menu.
Click to expand...
Click to collapse
I never had the phone to my face when I did my test calls - this was always phone in my hand and calling from my office phone.
I think I just came across a bigger problem - the dialpad doesn't work on incoming calls. I just called my phone from my office on the regular (not G-voice) number and pushed a bunch of buttons, and couldn't hear the tones.
You can disable the initial greeting and go straight to the call when you pick up. It is under Voice Setting in your google voice account. I know this doesn't address your unresponsive screen issue, but it's a temporary work around until your dialpad gets fixed.
bojackson63044 said:
You can disable the initial greeting and go straight to the call when you pick up. It is under Voice Setting in your google voice account. I know this doesn't address your unresponsive screen issue, but it's a temporary work around until your dialpad gets fixed.
Click to expand...
Click to collapse
Is this actually a bug? I posted another thread here and am trying to have people verify whether or not this is a real issue - if it's not a bug then I definitely need to replace the phone, 'cuz it's been factory reset as of last night.