Related
Hi, can anyone advise as to why I lose the all sounds on an Orange Branded M3100 phone, other that Microsoft voice command 1.6 no other software has been installed! The details of the ROM are as follows
Operator Version: 14.123.1.614
ROM Version: 1.23.61.4
ROM Date: 07/13/06
Radio Version: 1.06.00.00
Protocol Version: 32.37.7010.01H
Here what happens no sound on the phone, reset the phone sound is now back, after a while, don’t know how long but the sound disappears, you get no ringing sound, menu click sounds nothing, reset the phone again and all is back, so it would suggest that it’s not a hardware failure but a software failure, how can I stop the orange branding installing itself after a cold reset in case something there is causing the problem, has anyone else came across this problem?
This is a brand new phone only received it Friday, does it need to go back?
Kind Regards
Dogo
I've recently noticed on my 8525 too, after a while it seems to just go on silent but the setting isn't changed it still set to on and no sound comes out of the phone no matter what program is used.
Phew, I thought it was just me..
I have noticed it may be something to do with the Bluetooth ear piece, although it always seems to happen when I have left the phone a while. and never when I try to check for the problem
To isolate whether this is hard or software you could try doing a full backup. Do a hard reset and let the device run for as long as it would normally take to show the problem, without any additional software. But do run wifi and power intensive applications to warm up the device - as this can cause internal connector problems.
If the problem is gone, this will tend towards a software problem although not an absolute guarantee. There are some issues that are related to both soft and hardware!! For example the screen fading to white issue can be caused by running (power intense) software that makes the device warm and that in turn causes pressure to be put on the screen.
A final thought, the speaker connection block is next to the stylus tip. There have been cases of the inserting and removing of the stylus causing the connector to become loose. This can cause intermittent sound or no sound at all. The warranty voiding fix is easy. Remove back and check connection is tight. No further dismantling needed. Ensure camera toggle arm is engaged before putting screws back in. (Rear Speaker)
The front speaker can also have issues. has spring contacts that can become slack - poor contact with m/board. There is a thread on checking this.
Mike
No Sound, not a Stylus issue
8525, ms voice dial 1.6,
HTweakC 2.0,
SBP Mobile Shell 1.0.0 build 2632.
ROM 1.34.502.1
radio 1.16.00.00
This has been happening about a week, nothing new installed. On Saturday I missed 12 calls because it was "auto-muted" nothing was on mute, just no ring sounds or anything else. I thought it might be some setting, I suspected that it didn't come back after I had set on vibrate for a meeting, so I went through everything, looks good. had to soft reset for audio to come back. Happened again Yesterday morning after being on charger, had to soft reset, happened again this morning after being on charger, had to soft reset. I'm suspicious of the charge ciruits, the phone was placed on a night-stand and I checked to make sure sound was working AFTER i plugged the charger in (i am an on-call engineer for hospitals) when I got up this AM the first thing I checked was the sound, no sound. Had to do a soft reset and sound is fine.
THIS IS VERY, VERY, VERY troubling.
i cant say that my sound has been "loose"
thefunkygibbon said:
i cant say that my sound has been "loose"
Click to expand...
Click to collapse
yep, I agree. My keyboard slider might be loose, but never had problems with the sound.
No sound - possible solutions
I too have had the no sound problem, but I also have a solution (well it seems to work for me and a few other people I know)
I have found that if I have more than about 800 sms messages on the phone (combined count across inbox, sent items, deleted etc...) my phone will decide sometimes to stop making any sounds.
Other symptoms include thew screen not going back to the background when problems are "closed" (well press the X button), sometimes not changing from portrait to landscape.
Hitting the reset key temporarily fixes the problem, but it strike again at any time...
I have seen this on both the official UK orange firmwares
As a side note, more than about 1000 sms messages and 5 unread sms messages and the phone will lock up about 10 seconds after the phone boots up. You have to be quick when the phone boots to go in to the sms inbox and delete 1 message before the phone locks up. This can be a bit tricky but i have done it a few times
from readingmany related threads, it looks like there are several causes for this issue. for me, it was definitely microsoft voice command 1.5 and 1.6. I turned off any notifications from voice command and my problem went away. no calendar voice announcements, no callerid, no bluetooth routing announcements, etc. voice command simply doesn't give up control of the audio sometimes, and it appears to occur most when it wakes up and announces something.
All I use voice command for now is voicedial. try that a while and see if you are fixed.
1.5 was worse, but 1.6 does it too.
good luck!
wes
saga continues
It did it again, twice in one day. Picked up the phone, (it had been resting on the table for several hours). No sound, I tested by placing a call and turning speaker on.. this works! So the speaker (rear) is fine as well as the front (ear).
After I heard the speaker on speaker phone I tried hearing the dial tones or other sounds, none. No incoming ring.
Device and phone volume on FULL
Turn volume off, vibrate, on, off on, and from phone screen turn to vibrate then back to sound
Vibrate still works for inbound calls
Turn voice command off and on
Go to phone (in settings and play the ring I've chosen) and suddenly it’s working again?
I'll try the turning all but phone options in voice command to no-notify. But to tell you straight, this is silly, one more day of this and it's probably (unfortuately) crackberry city for me. I simply can't have a phone that doesn't ring. I guess some ittertation of an O2 would do.. but I'm not too keen on plopping down another 5bills....
any ideas?
labrati said:
It did it again, twice in one day. Picked up the phone, (it had been resting on the table for several hours). No sound, I tested by placing a call and turning speaker on.. this works! So the speaker (rear) is fine as well as the front (ear).
After I heard the speaker on speaker phone I tried hearing the dial tones or other sounds, none. No incoming ring.
Device and phone volume on FULL
Turn volume off, vibrate, on, off on, and from phone screen turn to vibrate then back to sound
Vibrate still works for inbound calls
Turn voice command off and on
Go to phone (in settings and play the ring I've chosen) and suddenly it’s working again?
I'll try the turning all but phone options in voice command to no-notify. But to tell you straight, this is silly, one more day of this and it's probably (unfortuately) crackberry city for me. I simply can't have a phone that doesn't ring. I guess some ittertation of an O2 would do.. but I'm not too keen on plopping down another 5bills....
any ideas?
Click to expand...
Click to collapse
I have just read your last two posts. I am wondering whether you are saying you have a sound/ringer problem OR whether you mean the phone sometimes crashes and therefore does not ring (i.e. you then need a soft reset) and sometimes you discover you've missed a call but never heard it ring.
If the above is true then I think you need to look for the solutions for avoiding hangs/freezing. I can guide you to these or a search will show them. It certainly does not appear that you have any physical problem with the speaker/earpieces.
Mike
dogo said:
Phew , I thought it was just me..
I have noticed it may be something to do with the Bluetooth ear piece, although it always seems to happen when I have left the phone a while. and never when I try to check for the problem
Click to expand...
Click to collapse
Hi, I never had a sound issue untill I started usin my HT820's, but have noticed a few times lately that my device sounds arent working, (I dont mean always through to the bluetooth headset) and I just power off/on the device, I dont get that many calls, so I havent missed any, and wasnt sure if it was rom or bluetooth related for sure, but I do usually leave my bluetooth on, just not always the headsets, it also doesnt happen a whole lot.
Loose connector
I'm not sure if this will help anyone, but i was losing sound on my 8525. I had dropped my phone twice and the rear speaker connection had gotten loose so i opened it up following the directions at http://www.howardforums.com/showthread.php?t=1152710&page=1&pp=15
and now i have sound again.
Continued Issues
Mike, thanks, the issue isn't with the phone locking up at all, it's been very stable, I think I've soft-reset probably 3 times in two months.
The phone literally will stop emitting any sounds. I can still hear if I place a call and if I place that call on speaker phone it's fine. However if you call the phone, try to play an audio file, etc there is no sound that emits from the device.
It did it AGAIN today, I tested, was able to place a call and put it on speaker and called it with my other phone, the pop up screen announcing the inbound call came up and everything else on the phone worked as it should (except no ring). I then went to settings phone and hit ok (top right of screen). BAM.. sound was working on the device again, inbound calls ring, able to play audio etc.
I did note one other possible anomaly, I have my PTT mapped to initiate voice command, when trying to use this I was unable to initiate voice command. After going to phone and pressing OK, voice command started working again. W/O voice command I'm sunk, I have 500+ contacts.
I placed a call to AT&T and I'm back on the "chronic retention" list.. ughhh.. I went through 8 treo's last time. I don't want another basket of refurbs to deal with, I like WM so much better than previous interfaces.. any ideas are very, very, very welcome.
-mike
More information
This morning, the sound was gone again, but I went into settings and started playing to see what else might induce it to work again, I tried voice command again, disabled and re-enabled, that didn't work.
I then went into sounds and that didn't work, went into Today, and Buttons neither of those worked, but when I went into input (didn't do anything, just opened it and closed it) sound started working again.
Hopefully, none of you guys have a newer ROM with the loud startup animation and attempted to turn down that volume via the registry as outlined in the wiki. Unfortunately, doing that also lowers the speaker volume so I just disabled the animation instead. Phone and bluetooth sounds fine but mp3 and everything else were also lowered to a whatever level depending on the startupanimation volume you set.
update
It did it to me again yesterday, this time only going to settings phone and pressing OK would make sound come back.
Today, the phone refused to dial or emit any sound. Would not come back after soft reset (would not dial, no sound) had to do a hard-reset (removed battery). After first soft reset a windows came up to advise that mobile voice command couldn't start...
For a darn near $500.00 phone this is pretty sad. Love the phone but gee whiz...
Daily occurance
Well, it does it every single day at least once a day, and I've noticed the phone has slowed a lot, sometimes during SMS or email the cursor goes away or I have to wait 20-30 seconds for words to complete typing after I've finished. I guess I'll get my refurb next week. Perhaps go back to palm.. dunno...
possible fix?
I turned OFF the SMS message sounds and it seems to be working w/o losing sounds again! I'll let it run for a couple of days and see if this is the deal, but I now have no audio announcement for ActiveSync, POP email, SMS, or MMS. I do have audio/vib for missed calls. Anyway, it's been up and running fine all day. Good Grief.
no fix in sight
On hold with ATT right now for another phone. It did it again today at about 10AM. Strange, it may be time sequential, but it didn't do it at all yesterday.. it was great to have the phone ring.
Anyone here use VC1.6 with Bluetooth?
Has anyone else noticed that the confirmations don't work?
I've seen threads on other forums about this, but no solution yet over there.
Figured I'd bring it up in case folks here have the answers.
Basically, here's my conversation:
Press BT button
Device: *Beep*
Me: "Call John"
Device: "Call John?"
Me: "Yes"
Device: *Timemout Beep*
Now, the confirmation works when used on the device just fine.
When on the headset, its like it gives up without trying to hear me.
MS Voice Command v 1.6 works almost perfectly on my Sprint Mogul. It has one flaw - when the button you map is first pushed it does not give off the beep, but the small microphone on the top bar shows up. When the little mike shows up, you can say your commands and it works perfectly.
The next time the button is pushed, the beep is heard and the mike shows up.
Also, VC is activated by my Motorola S9 stereo BT headset. If I push the right button on the headset, I hear the beep and can give the command into my headset even if the headset is in my backpack.
The failure to beep on the first button push is a small problem I'm sure can be worked out. For me it is no problem at all. I just push the button and begin speaking.
I own many other HTC products and VC works as well on the Mogul if not better than any of them and I haven't even hacked it yet.
The problem only shows up when dialing a number from the BT headset and the confirmation is played back. It seems there is a problem with the mic after the confirmation is played so you can't reply "yes" or clarify. It works fine for opening programs or if the confirmation is turned off and you are lucky enough for it to hear you correctly
ImCoKeMaN said:
The problem only shows up when dialing a number from the BT headset and the confirmation is played back. It seems there is a problem with the mic after the confirmation is played so you can't reply "yes" or clarify. It works fine for opening programs or if the confirmation is turned off and you are lucky enough for it to hear you correctly
Click to expand...
Click to collapse
Yeah, this makes browsing media impossible!
I used to say "Play music" wait until it asks me what type to sort by "Artist"... wait again "Dream Theater"... and then the music would start.
Now, I can't get past the first prompt because the mic is shut off. Very weird indeed...
Voice Command 1.6
One thing that I've noticed with my S9 and 1.6 (wm6 but had similar issues in wm5) is that VC gets confused by the stereo headset, announcements will generally shut off the headset for a moment and come out of the phone speaker, if I hit the button on the headset, I will get the VC beep in the headset, but it seems to be listening to the mic on the phone, and if I hit the phone's activation button, the beep comes through the phone, but it then seems to be listening to the headset for commands. I've found no reliable way to 'straighten' this out, however, I did notice the other day when I reset my phone and used the 'play' button on the headset to reinitiate the phone/headset connection rather than initiating it automatically when I turned on the headset that it seemed to be functioning normally for the first time in a long time. I've not tried to reproduce that yet, but will try it tonight.
Traumtanzer said:
One thing that I've noticed with my S9 and 1.6 (wm6 but had similar issues in wm5) is that VC gets confused by the stereo headset, announcements will generally shut off the headset for a moment and come out of the phone speaker, if I hit the button on the headset, I will get the VC beep in the headset, but it seems to be listening to the mic on the phone, and if I hit the phone's activation button, the beep comes through the phone, but it then seems to be listening to the headset for commands. I've found no reliable way to 'straighten' this out, however, I did notice the other day when I reset my phone and used the 'play' button on the headset to reinitiate the phone/headset connection rather than initiating it automatically when I turned on the headset that it seemed to be functioning normally for the first time in a long time. I've not tried to reproduce that yet, but will try it tonight.
Click to expand...
Click to collapse
Scratch that, I wasn't able to duplicate this, so seems to be a random occurrence, I know that every once in a while it does seem to work correctly, but that's very rarely.
List of Voice Commands
Has anyone got a list of voice commands, and is there any way to add new commands?
My VC 1.6 bluetooth problem is even more frustrating. It always recognizes my contacts, but the confirmation doesn't work AND I CAN'T DISABLE IT!
I uncheck the confirm box on the VC settings, but it still tries to confirm.
Is there something I'm missing?
Sprint does it again
WM6 has voice command built-in, but Sprint decided to disable it and not make it part of the ROM, so when you install 1.6 over the already there application, is when you lose part of the functionality.
Ha! I found my voice command problem -- I had a duplicate contact.
What voice command said (even after I turned off confirmation) was "Joe Blough at Home 3 found" and then it displayed one of them. When I removed the duplicate and turned off confirmation -- IT WORKED!
Now, if they would just fix the confirmation to work properly...
Ok.....my problem is it will not announce incoming calls, no matter what i do...everything else seems to work fine, but it will not announce incoming calls threw the bluetooth nor speaker, am i missing something???
Bottom line: Voice Command 1.6 is buggy, and needs to be updated to work 100% with WM6. Start complaining to Micro$oft.
TC1 said:
Bottom line: Voice Command 1.6 is buggy, and needs to be updated to work 100% with WM6. Start complaining to Micro$oft.
Click to expand...
Click to collapse
It's not buggy at all, it wasn't made for use on WM6, it's for WM5, we're lucky it works as well as it does.
You can bet MS is already working on a new version, question is when will it be released.
Is there an echo in here? What part of "needs to be updated to work 100% with WM6" didn't you understand?
I was saying it isn't buggy as you said, it works great for the OS it is intended to be used on.
Funny enough, VC works great for me... The only issue I have is sometimes it does not play the first tone when I press the VC button...
Shaska said:
Funny enough, VC works great for me... The only issue I have is sometimes it does not play the first tone when I press the VC button...
Click to expand...
Click to collapse
It works fine if not using bluetooth. (aside from the missing first tone sometimes)
Dishe said:
It works fine if not using bluetooth. (aside from the missing first tone sometimes)
Click to expand...
Click to collapse
And also doesn't always confirm commands. At least from my experience.
primenall said:
It's not buggy at all, it wasn't made for use on WM6, it's for WM5, we're lucky it works as well as it does.
You can bet MS is already working on a new version, question is when will it be released.
Click to expand...
Click to collapse
I have the Alltel 6800 with WM5 and am experiencing the same problems as you WM6 folks.
It seems to be an issue with the Mogul/MSVC combo like you said, also a friend of mine put the WM6 Rom on his 6700 and he says MSVC confirmation works fine.
Maybe a Radio incompatability, I'm just a novice though?
Hey there,
I have seen connectivity issues, but not this particular issue so...here goes:
This problem has been sporadic for me, but recently lasted for the past week.
I can connect my bluetooth earpiece to my HD2 just fine.
If someone calls I can hear it through the phone and pick up.
I can have a conversation through it.
What I cannot do at this time (and could a few days back) is press the button on my earpiece, hear the "blip" which prompts me to speak, say call [insert name], hear the name repeated back to me, I confirm and away we go!
If I am looking at the phone while I am doing this the microphone symbol will show up when I press the button.
If I then say, "Call home" it will show the contact page for "home."
If I then say "yes" it will dial "home."
All of this is done with no sound confirmation.
This is obviously not good for hands-free driving!
I have changed no settings and yes, it has been working with all ROMs, but as I noted, I have had this problem sporadically and now it is going on a week since I had this functionality.
Yes, I have done several soft resets, turning bluetooth on and off as well as unpairing and redetecting the device.
Any thoughts?
OK...it just worked for me.
Like I said...sporadic.
The only thing I can think of that I did differently was that I turned on bluetooth then turned off the phone (just clicked the power key, did not power down) then put on my bluetooth and once paired I tried the function and it worked.
The last few times I had not clicked the power key as I was waiting for the pairing and then attempting to use the function immediately thereafter.
hmmmm...
I don't know if this counts as a "fix" yet.
Hi everyone,
First off, I'd like to start by wishing to everyone happy Holidays!
I have been literally searching all over the Internet for any information regarding the issue I am about to describe in detail and since no solutiuon was found, there's nothing left for me to do but ask for help, and hopefully get the right answer. That's why I want to be as specific and informative as I can.
The problem I am having is this; I recently purchased a new Jabra Motion bluetooth headset and decided to start using the voice dialing function on my Galaxy S4, since it works very well (when it works) and is really a breeze, especially while driving.
In short, the problem is that the S4 completely loses audio (other party hears nothing as well) after initiating a call, via voice dial commands through any bluetooth headset (I'll get to that). When that happens, the phone has no in-call audio whatsoever (with headset on or off, with speakerphone or earpiece on), no matter how many times I start or receive a call and nothing brings audio back, except a reboot from the i9505's power button menu. All other audio works, like videos, unlock sounds, ringtone, music, even the little chirp right before the other party's phone starts ringing and the hangup chirp can also be heard. The worst part is, that it occurs completely at random, it can happen on the 1st time I voice dial or the 10th time, for example. The problem has not shown itself, when initiating a call normally or picking up with a headset connected, before audio gets lost.
Before purchasing the Jabra Motion I've been using an earliest model Jawbone Icon and had never even tried the voice dialing feature on any previous phones or the S4. After encountering this problem I tried to test whether or not it would happen when using that headset, the result was yes, so it is safe to say it will happen when using any bluetooth headset, with the same randomness.
This is what both headsets launch on the phone, when attempting to voice dial:
View attachment 2474439
The phone itself is a completely stock and un-rooted 16GB Galaxy S4 i9505, running the latest available Jelly Bean 4.3, build: XXUEMJ7.
The headsets are always connected to 2 devices simultaneously (in case that might shed some light)
What I've tried so far (no difference made, at all):
- Toggled bluetooth off and on
- Tried unpairing and re-pairing both headsets on both phones, or only on i9505
- Tried factory resetting both headsets
- Tried to toggle, while in call, between speakerphone, earpiece, headset, turning off headset and all possible combinations
- Removed Jabra companion app and services app, then reinstalled, then tried without the apps installed.
- Cleared cache from both Jabra apps.
- Cleared cache from system apps such as dialer, bluetooth and Google Search.
- Contacted support of both Samsung and Jabra (huge waste of time)
Sorry for the very long post, but I want to be clear and comprehensive as possible. Any help would be highly appreciated.
Please no factory reset suggestions, I am aware of that possibility, but do not want to go through all the trouble to set up tons of apps and stuff again.
Thanks in advance to anyone willing to help!
Anyone?
Please?
I have a stock, non-rooted Verizon GN3, which behaved pretty much flawlessly in general, and with Bluetooth Headsets in particular, prior to the KitKat update.
This behavior occurs with both my BlueAnt S4 Visor device, and a Bose Series 2 Headset. When I turn either on, it quickly connects. With the phone locked, screen off, if I initiate the connection from either device, the Voice Dialer comes up, and I can initiate a call. The call connects, and I can hear and speak through the Bluetooth device. Everything works as expected.
But if I then try to make another call, it takes at least 2 additional tries to get the Voice Dialer to come up. The first time, the screen comes on briefly, then turns off, sometimes with the grey screen preceding the Voice Dialer briefly appearing. After a couple of more tries, the Voice Dialer comes up.
But after I have it place a call, the audio send/receive stays in the phone, and doesn't transfer to the Bluetooth device. This pretty much defeats the purpose of having it in the first place!
If I turn off either Device, turn it on and reconnect, the same cycle starts up again. It works properly the first time, but messes up after that.
With the BlueAnt S4, I removed the pairing from my GN3, effectively deleting the device, and then turned off the phone. I then did a complete reset on the S4. Turned the phone back on, re-paired, but this didn't fix it.
This is extremely annoying, to say the least.
I have examined all my settings, and they seem correct. I went to Google Search settings, Voice settings, and tried it with the Bluetooth headset ('records audio through Bluetooth headset if available') both checked and not checked, and observe the same behavior.
I welcome suggestions on how to fix this, and getting it to work consistently and correctly, as it did before KitKat.
I would consider a factory reset on the GN3, if I were convinced this would fix the problem. But I'd hate to go through that hassle, and encounter the same problem again.
I have noticed several anomalies with the kitkat update. I was hoping there was a way to roll back the update
Sent from my SM-900V, unrooted
Well, I've made some progress, and I think the problem originates in a recent update to "Google Search." I found many reports of Bluetooth related problems that were remedied when the update was rolled back.
So, I went ahead and rolled back the Google Search Update, and in fact, went ahead and Turned if Off completely.
I tried out my Bluetooth Headset (the Bose earpiece, haven't tested on the BlueAnt yet), and it works perfectly, as before. And better yet, when I touch the BT button, S-Voice comes up, rather than the plain Voice Dialer, so I can not only place calls, but initiate navigation, send a text, or whatever I would like to do. And it seems to respond each and every time.
We'll see what happens over time, and if there are any unanticipated consequences to turning Google Search off, but so far so good.
If this turns out to be the answer, it will be a Google Search issue (which would hopefully be fixed over time), rather than a KitKat issue as such.