Database Users

MDA Compact II and no sound

All,
I have a MDA Compact II using the latest T-Mobile ROM and experiencing a problem regarding incoming phone calls and text messages notifications. I have set the phone to ring full volume and text messages are assigned to an audio notification. Occasionally when I receive texts/phone calls there is no audio notification even though they are switched on. I am missing quite a few phone calls and the only way to get the audio notification back is to soft rest the phone.
Does anyone know how to get around this?
Thanks
M

Just to say I have exactly the same problem. phone working fine for 3 months then sound only after soft reset, then stops working after a couple of days. i cant attribute it to any event

U2 have probably a program installed which is eating up sound handles (i.e. not releasing them after usage). A soft-reset releases them of course. So you have to uninstall some 3rd party software to find the nasty one...

No Audio
Hi
Am running a T-Mobile Compact 2 with WM5, also installed is Spb Pocket Plus
I have no audio for any Windows Media Files or for any sounds / notifications e.g. the alarm. I do get audio playback and notifications through wired headphones. The phone will ring and vibrate when called.
2 Soft resets and the removal of an Alert progam unwittingly installed from Skyscape (medical and nursing texts for PDA) have not resolved the issue.
I have been into sounds and notifications and ticked all the relevant boxes. Interestingly in notifications I ticked the box for the device to vibrate when using activesync. It was vibrating but not making any sounds earlier.
One of the seniour guys at Pocketnow.Com has suggested that I have somehow turned down the speaker volume. If so - how do I turn it back up? Trust me when I say that the standard volume display shows volume at full.
Any ideas?
Will.

Hi
I've just got back into work tonight and synced with my work PC. When active sync started up the audio came back online. I have no idea why.
Any deas?
Will.

Still No Audio
Hi,
Last night the audio on my T-Mobile Compact 2 came back online when I was synced with my work computer - great! I even unplugged the USB lead and audio remained. I then resynced and carried on listening to headphones for a few hours while I worked. When I disconnected I found that Audio had died again. I therfore assumed that it was an issue with Activsync 4.1. I deleted the sync relationship on both my device and the PC, did a soft reset and created a new one. Still no audio.
Does anyone have any ideas about what is going on? I am thinking about a hard reset if no one has any thoughts.
Will.

Hi,
have just tried calling my deviced from a landline, what i've found is that the device will ring but that I am unable to communicate using it (Can't recieve or send voice) unless I use the wired handsfree kit. Have not tried a bluetooth headset.
Will.

Sound problems with telephone
If your PDA works when playing sound files but you cannot hear anything when telephoning, the problem is usually bad contacts on the phone earpiece.
The PDA has 2 speakers, one for sounds and a smaller one for the telephone.
You must open up the animal and clean the contacts on the motherboard.
Hope this helps.
Bob

I have the same problem...sound is often working normally, but sometimes it just stops for a few days or longer. It is very annoying to always take the wired headset with you. Soft-resetting does not help in my case. I also have SPB pocket plus installed and a wireless network SDIO card. I could however not find a general rule that makes the sound stop... e.g. installed software or activesync problems.
I read earlier about cleaning up the speakers, but I have no idea how to open up the phone. Suggestions?

It could be the problem from the wired handsfree jack/socket, once you are taking the pin out, the socket is not switching the device speaker functionality back.
The picture attached is for illustration only, and the functionality is to cut all the sounds from the device and through to the hansfree, and once the handsfree is out then to restore the device's original sound system.
Not 100% sure but someone can try to clean the jack without opening the device.
1. Switch-off the device, remove the battery, leave it for 10-15 minutes.
2. spray a minimum quantity of CONTACT CLEANER ( http://www.maplin.co.uk/Module.aspx?ModuleNo=4153&criteria=contact cleaner&doy=15m11 )
3. Leave the device again for 10-15 minutes to evaporate any moisture
4. Put back the battery and try now.
GoodLuck
Sidd

Has anyone tried yet??

yes, hands-free socket could be the problem
My beloved Jam suddenly lost sound yesterday, and it does seem to have been caused by a physical failure inside the hands-free socket. I was able to fix the sound by opening up the device, opening the little black box that houses the socket, and tweaking the contacts.
All sound suddenly disappeared except for bluetooth and the wired hands-free earphones. Without using those accessories, there was no phone audio, no sound from speaker (from ANY source), and--interestingly--the mic did not work at all. But calls worked fine through the BT headset, and all sounds from all sources came through the wired earphones when they were plugged in.
This evidence all pointed to the existence of a switch inside the hands-free socket that was stuck, telling the device to send all sound to the wired earphones even when they weren't plugged in. After opening the device and the box that houses the socket, I pried the contacts a bit with a pocket knife, hoping to ensure that when the there's no jack inserted in the socket, the device will know it. Sure enough, after I put things back together, sound is once again functioning properly. Whew!
BTW, the problem started after I took the Jam skiing so I could listen to music. It might even have been caused when the earphone jack was violently pulled out at one point. Anyway, I had already decided not to try that again, because the Jam seems to stop functioning reliably above 9,000 feet.

Hi, I had the same problem as all of you, what i did to fix it was...
1. plug in handsfree
2. pull handsfree ^up^
3. now slowly pull out
This should cure the problem as it cured mine

thousand thanks to Ayyub and mtn_lion. i'm glad i went to page 2 of this topic. now i can invest my time for important projects. the importance of sharing ideas in this world will help evolving each other without having to go through the same paths again. to everyone reading this: it's okay to share your painful steps even though you didnt find a working solution! dont make others do the same mistakes over and over again. support the evolution. it could save your life and millions of others soon or later.
polar20

We have to thank everyone who posted in this topic. Without them, we would mostly still be struggling. Great contribution folks!

same problem here
I, too have an t-mobile MDA and have had the same exact sound problem with and and have exchanged two with t-mobile - all three lost sound after a day or two and the only thing that brings it back is a soft reset. I do NOT use a hands free unit pr plug anything into the headphone jack so that's not the problem. T-Mobile claims to know nothing about this problem....
Jim
Littleton, CO

well, i was experiencing the same problem when uninstalled "pocket zen phone" application. after uninstall, charmer sometimes lost sound completely and only softreset brings the sound on again. hardreset solved this completely, not using PZP anymore...

Hi I have this same problem with my T-Mobila MDA Vario II, it did hapen before to me but i just did hard reset and thath solved the problem, but this time it didn't helped. I allready reflash MDA with 3 different systems and still this same, i was trying to plugin in and out handsfree kit but that didn't help. MDA doesn't have any sound now, only thrue handsfree kit. Is any one have any more ideas what i can do?

It unblocked it self after 24 hours lying on the shelf, so still don't know what's couising the problem.

[Q] Very specific problem with voice dialing from bluetooth headsets

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?

[Q] Flaky Bluetooth Headset Behavior since KitKat

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.

[Q] No Sound During Calls

Randomly when I make calls or receive calls I have no sound. I can't hear them and they can't hear me. Rebooting the phone will fix the issue for a short while. I have been able to reproduce this by connecting to my cars blue tooth and making a call. The 1st call works however all calls after the first call I have no sound again. When the phone in the no sound state (Phone Call) Bluetooth media still works just no sound while in a call. The speakers work because I can play music and the mic still works because I can still record sound. This issue seams to be related to the phone app its self???
My phone is a Samsung S4 (AT&T) with Android 4.4.2 (Rooted via Towelroot) with SuperSU by chain-fire installed.
Here is some of the trouble shooting I have already done.
1. Factory Rest the Phone via Stock Recovery (Still can reproduce the issue)
2. Played around with various settings i.e. Google Now Bluetooth options. Un-paired all Bluetooth devices and then re-paired one to try (Still having same issue)
3. Cleaned out all app cache (Still having same issue)
4. Re-installed pre-installed apps that I removed once rooted.
Long story short, this one has be baffled. The only thing that fixes the issue is re-starting the phone.
Thanks in advance for any assistance
AG007

Same Problem Here, I may have figured it out:
After I rooted I used some apps to auto kill some running, supposedly non-essential apps. This caused my phone call problems, same exact issue as you're having. A reboot fixed it for me as well. I will let you know if it happens again without closing any apps.......

Sound output disabled while sleeping (S7 Edge G935F)

Hello gals and guys, you are my last hope.
I have a Galyxy S7 Edge G935F bought in Germany with no sim lock, i got it with G935FXXU1APAW, updated to G395FXXU1APC8. Yesterday i rooted it with CF-Auto-Root-hero2lte-hero2ltexx-smg935f based on XXU1APBF. I still have stock recovery.
The Problem:
Sometimes, while sleeping, the phone disables all sound.
This happens mostly while recharging, but it happened also while simply sleeping and not recharging. It is not reliably reproducable, sometimes the phone works for 2 or 3 days without the error occurring. Which makes the error very hard to find of course.
Sound off means: No media output is working (games, video, music), notifications are not sounding only vibrate, the phone doesn't ring when someone calls, just vibrates. No calls and notifications means, this is very severe.
When i plug in earphones or headphones, there is also no sound on the headphones. Putting in and pulling out the headphones does not reactivate the sound, so it seems not to be a problem with the headphone jack. The jack is very loose, though, doesnt hold the headphones strongly; but thats another problem.
The sound can be reactivated by the following:
- rebooting
- calling someone (i used to call my provider) or getting called (the first call gets lost, but when i get a second call, it works again)
- i installed an app called SoundAbout, which lets me route the sound to different outputs. I must first route media output to "earpiece" (the small loudspeaker you hold on your ear during calls) and then route the media back to "Speaker". Only this combination reactivates the sound again. Just activating "Speaker" or any other combination like for example first "Wired Phones" and then "Speaker" does not work. It must be "earpiece" and then "Speaker".
What i tried, without success:
- deleted all bluetooth devices
- disabled bluetooth
- enabled "prevent USB audio routing" in dev options
- uninstalled all kinds of apps having to do with sound or lockscreen
- played with all kinds of settings having to do with sound or lockscreen
I searched everywhere. A call to Samsung was not very helpful either. I might have to try a factory reset after all, but even if its good at factory, i still won't know the culprit.
But since the problem can be solved via software, i suspect it is software related or is at least diagnoseable via software.
Of course, it would be insanely awesome when someone could just present me the solution, but i would do all the debugging myself, if i only could.
I am a developer myself, but only on windows. My experiences on linux don't go much further than doing an "ls -la" on commandline and i am a total noob on android. I will not be afraid of using a terminal or adb, as long as i am guided a bit.
I hope, somebody can point me out how to diagnose and this thing.
Can one diagnose the current state of audio routing ? Can i manipulate it via commandline ? Are there other relevant components which i need to query ?
Could i write a script that pulls those queries every minute or so ?
And finally, if the wrong settings are found, are there log files which can point out who messed with those settings. Which apps would you recommend for those actions ?
Thanks to everyone in advance ...

Correction
just getting called doesn't fix anything. Only when i accept the call it gets fixed and then the next call rings again, of course. So this means, while the bug is active, i miss all calls.