Develop Bugs

[Q] No Sound via Speaker, Headset, or Bluetooth

Hi everyone, I'm hoping someone has a suggestion for me wrt to audio problems with my wife's Sprint Galaxy S3.
On a fully stock up to date S3, about 3 days ago all sound stopped working, this includes alarms, answer calls, key press sounds, playing music. However after a reboot, it would start working again for 6 hours or so, and then quit again. I assumed this was a software issue of some sort. I have an older rooted phone which I love and have had for years, I suggested that we finally root her S3, so she could get all those benefits plus fix whatever little software problem this was.
The rooting process when fine, and the phone now has CWM and CM 10.1.2 (Android 4.2.2). However the audio issue is still there and in fact a reboot no longer fixes the issue.
I have tried pluggin in the ear buds w/ built in mic, and those too fail to work. I also have paired various bluetooh devices like mini boom boxes etc.. they all pair fine however there is no audio output from them. No audio in the dial pad when hitting the numbers. When trying to play music the DSP Manager will crash, and then the music app crashes (tried Apollo and Google music). If I go to the sound recorder and hit record, it pops up with "Internal application error.".
So it seems all audio (speaker, mic, bluetooth, and headset) is broken which again makes me think software, but even after rooting and installing a new rom like Cyanogenmod the issue is here.
Any thoughts on what else I can try? Any firmware updates that I could apply specific to audio issues like this, or perhaps it is some sort of hardware issue that is preventing the software drivers from behaving properly?
thanks,
fishtek

I would Odin back to complete stock and see if the issue still arises. If it does then it could be hardware related.

Same problem
metalfan78 said:
I would Odin back to complete stock and see if the issue still arises. If it does then it could be hardware related.
Click to expand...
Click to collapse
I have that sane issue and nothing I do seems to work.

[Q] S3 4.3 AT&T S-voice no longer works with Bluetooth mic.

Well, I dug myself a hole by allowing the OTA to 4.3.
On my AT&T S3, SGH I747, I was running 4.1.1 stock rooted, with a toggles mod, and the At&T update got pushed to the phone one night. It could not get past TWRP so I swapped back to a stock recovery. The update ran again, and failed at about 25%. I didn't think anything of it since the phone worked fine, until I discovered that I could no longer change the icons on the lock screen (settings would stop working). So, I installed Kies (which it turns out will not connect over a USB 3.0 port, but thats another wasted couple of hours and another story) and backed up my accounts, settings, etc.
I then flashed to a stock 4.1.1, and then allowed the OTA update to 4.3. This time it went (Yay..sort of).
So, I'm looking at the new features, and finding some useful and overall enjoying thew update, but ran into trouble with S-voice and bluetooth, specifically, the microphone in my car. This used to work. I could press the mic button on the cars Nav unit (Parrot BT) and I could say "call "X" mobile" or "play Concrete Blond" and the phone would do what I told it to, more or less.
Now, It will not connect to the mic, I get a brief message "Check in-car audio" and after 3 seconds the car reverts to playing music (it mutes when you press the mic button). The other BT functions work. My contacts are transferred, I can force music to the unit, I can place calls and we can hear each other, etc.
After a bit of reasoning, I began to zero in on S-voice as the culprit. I confirmed this by installing Bluetooth connect and pointing to Google search when the mic button is pressed. This allows me to make calls via voice command, but that's all.
I used this feature a lot., probably 3rd or 4th down on my priority list, after phone and camera. I'd like to use it again.
Here are my options as I see them.
-Leave well enough alone and wait for Sammy, or my Navs mfg to fix their stuff and use google search instead for now. (Will they do it faster if I hold my breath?)
-find a 3rd part app to make S-voice do what its frikken supposed to do. (Not sure if their is one)
-find an older version of s-voice and install it over the current one, which may or may not work. This would require that I have a working backup plan in place and since I understand that the bootloader I now have (MJB) is a one way trip, this limits my options. (can't flash back to 4.1.1 and don't have a 4.3)
So... does anyone have..
-any sympathy? (It's Christmas day)
-a solution to my problem?
-a recommended app to patch this?
-an older version of S-Voice form a S3 phone?
-info on any of the 4.3 roms floating around (can they be installed over a stock 4.3?)

I'm having the same problem. I didn't know S-Voice was broken until I did a factory reset last week to fix problems with T-Mobile wifi calling. I had been using Utter! for voice control, which has pretty good voice recognition, but randomly stops working with bluetooth. Since I hadn't tried S-Voice for a long time, I wanted to see if there had been any improvements. Once bluetooth is connected, the S-Voice mic button is disabled and the bluetooth button has no effect on it. I may end up going back to Utter!. Unfortunate, since almost every option except S-Voice is just too open-ended for use in the car. I don't want to ever be required to look at or touch the screen. For all the complaints I have seen, nothing can top Sync in my Ford. Voice recognition is excellent and everything can be done by voice.

well, I'm glad at least I'm not the only one. after some experimentation, I bought an app called Klets, which works with specific music players, Poweramp being one, so I got it as well. I had no luck with utter.
Klets works using google's voice recognition engine and works well. You can add custom commands to the already huge list it has. Well worth 2 bucks! Like all VR apps, it has issues with background noise. It is also written by an Italian, so some of the translations are a bit off. When calling a contact, you get "I'm starting to call towards (contact)"
Poweramp also has the advantage of boosting the volume a bit, which helps with the car since the input volume for BT is set so low, or BT output is low. Either way, it helps. Plays FLAC too.

[Q] Clear, un-garbled Bluetooth phone calls ?

Can anyone recommend a ROM where the in-call audio through Bluetooth connection is clear like it was before they rooted their HTC1? I really love my current ROM, and really most of the ROMs I've been using for the last year or so, but my customers are always complaining that they can't hear me or that I'm garbled and breaking up. I spend 80% of my work time in the car and need a better solution.
I don't care if it's Sense based or GPE or what.

Most sense or gpe roms available for this device, Bluetooth works just fine.
The part you need to be sure you did, was to update your firmware.
Using old firmware is the number one reason for in call audio issues, whether speaker or Bluetooth.
I can say with certainty, that it works on all my sense and gpe roms.

My experience with kitkat on i9300i

These are my experiences with kitkat 4.4.4 after I flashed it on my I9300I:
1. Frequent dropping of 3G signal on 4.4.4.
- I tried 3 variants of the 4.4.4 Kazakishtan, Hongkong and UAE but I still experience frequent drop in 3G signal. I had in some instances to reboot the phone to get back the 3G.I have not experienced such on 4.3 that came with the phone.
2. Weak Bluetooth:
- I use a Jabra clipper bluetooth stereo earphone. When I listen to music with the phone on my pants pocket the music sometimes stutters. I had to hold the phone up with my hand to get a better sound. Again not experienced on 4.3
3. SMS blocker not working on 4.4.4
- I use 2 SMS blocker apps- Mr. Number and Phone Warrior. Mr Number states clearly that it does not work on 4.4.4. Phone Warrior works only if it is used as default messaging app. Not good as it is not customizable- fonts are too small plus you cannot assign tones to the allowed contacts.
4. Viber causing the default camera to fail.
- The camera was working ok until I installed Viber. Then I got "Unfortunately camera app failed to inialize" error. I googled about this and found out that this is a known issue with Galaxy S3. However this does not happen on 4.3 so again a kitkat related issue.
There may be more issues still not experienced but since I use my S3 Neo for my daily phone I had to go back to 4.3..
How about your experiences?

[Q] Sound + Root Issues on Z1C

Hey folks,
So I have a problem with my Sony Xperia Z1C (D5503), and would appreciate some input on my theories as to how to fix it, at which I have yet to be successful.
I live in China, and I bought my lovely device on Taobao a few months back for a very discounted price (risky, of course, and to be certain this is where the issues stem from). I purchased the Hong Kong version instead of the Chinese version, because the Chinese version is built to block Google Play by default and comes with a bunch of junk apps. Anyway, I was stupid and didn't get a chance to use it before the seller's 7-day return policy was up, so it was too late for a return after I found out about its issue.
The issue is this: when I receive a call, the caller cannot hear my voice. Not that it's completely silent, it's just muffled and quiet. I've tried various things, turning on and off the Microphone Noise Suppression option, adjusting the caller's sound options, but nothing; it seems there's a defect with the microphone. When I switch to speakerphone during a call, however, there are no problems. On a related note, the same thing is true when I use apps like Skype and particularly WeChat: if I send someone a voice message, they can barely hear me. Only when I use a headset are there no problems. So, to continue using this phone, I've succumbed to bringing my headphones around with me and plug them in when I receive calls or have to send a voice message.
So the microphone's screwy? Interestingly, when I record with other apps, like the Sound Recorder app, there are no problems. It picks everything up perfectly. It must be recording on "speakerphone" for this app, if that makes sense; right?
Anyway, I was wondering (hoping) if the kernel loaded on my phone has anything to do with it. It's the stock kernel but one that seems to be used more for the Xperia Z1. Since I'm mentioning it, here are all the specs:
Model: D5503
Android Version: 4.4.4
Baseband version: 8974-AAAAANAZQ-10270054-61
Kernel version: 3.4.0-perf-gaee6e5a [email protected] #1 Thu Oct 9 09:14:33 2014
Build Number: 14.4.A.0.157
Anyway, I still have this hope that the problem is fixable. I am inclined to wait for the rollout of Lollipop for the Z1C, but that could be months, and this has been going on long enough as it is.
I'd appreciate any input, especially if you think I'm on (or not on) the right track thinking that flashing a new kernel may make a difference, assuming it is a conflict with the firmware. Or, perhaps I should just accept that I was sold a defective product for a decent price (I mean, everything else is working OK...).
Should also add, running the service diagnostic test for both primary and secondary microphones provides clear, audible results.
A few additional details, that may be of interest: my phone is rooted, with SuperSU as the app. The stock version of the app is a system app, but when I update the app, it loses its system app status and also does not successfully update the binary. I couldn't install busybox for the longest time but was finally able to do so through the advanced root options FlashTool. This is interesting, I think. Also, there is no recovery mode.
Thanks for your time!

jujube123 said:
So the microphone's screwy? !
Click to expand...
Click to collapse
Looking at the Sony forums there are a lot of complaints about muffled calls and poor microphone on voice calls, with no comment from any Sony moderators, which isn't a good sign.
One suggestion was to turn off the "Microphone noise suppression" option in call settings. Another was to not have the call on speakerphone.
Someone else suggested editing build prop, which if you've got a rooted phone should be easy.
persist.audio.fluence.voicecall : false
I think this turns the audio post processing off.
You should get recovery working, try installing the latest recovery from NUTs dev page, this installs from your PC. This will help you get a working SuperSU as it will restart in recovery mode.
The file you are looking for is called
Z1C-lockeddualrecovery2.8.2-RELEASE.installer.zip
Once you have recovery you could do a nandroid backup and experiment with a factory reset.
If all that fails, it looks like it's a problem limited to Sony stock builds, so it might be worth experimenting putting a CM rom on your phone. Obviously read up on how to do this properly, and make a copy of your TA partition so you can back to stock if you change your mind.
This page is a good place to start.