So I just noticed that with RC4 (clean install from the Stock image) that I can't change my volume through my BT buttons (Jabra Clipper), which has worked with past releases.
Has any one else run into this issue? I will most likely back up my current image and install a clean RC3 or pre-RC3 image to verify it, but I wanted to throw this out there in the event someone else might have the same issue.
Related
Hi ll,
I really out of ideas here .
I was running Pays 1.9 Bravesoul ROM without any issues for about 4 months on my unbranded Desire(HBOOT 0.75)!
Today I decided to update to Froyo.
I used Rom Manager to upgrade to OpenDesire 3.03 and Radio 32.43.00.32U_5.09.00.20.
Every thing went well, except that I noticed that the MIC doesn't work at all.
Not when I make or receive a call, Not if I try to Mute/Unmute it, Not if i try to Record sound, or Video or WHATEVER!!! The only way the other side can hear me is trough my BT headset.
So I tried to use the LeeDroid 1.7a ROM but same result. Also tried to use different Radio - 32.42.00.32U_5.09.00.08.
I then Nandroid restore to my 1.9 Pays rom (Wiping Data+Cach+ext), but still doesn't work. I tried different Radios:
32.37.00.32U_4.06.00.16_2
32.36.00.28U_4.06.00.02_2
32.26.00.24U_4.04.00.03_2
same thing...
I finally Unrooed my Desire to v1.15.4 Radio 32.30.00.28U_4.05.00.11 without any luck!
So I'm pretty hopeless Please if someone also have / had this issue, Please share!
Thanks!
sounds to me like it's broken mate
i know it's coincidence that it broke as you changed ROM but if it doesn't work on anything there's no explanation
have you tried a hard reset + clearing caches?
if you have then unroot your phone, put it back to your original RUU for warranty purposes and sent it back for repair
by what do you mean Hard Reset?
I wiped all data, I've changed roms.
Currently It's unrooted...
Is it possible for the Radio update to do this? (all the updates went without a hitch)
Or maybe the OpenDesire ROM (I see that v3.03 is removed, do you know why?) did this?
There is no way it a coincidence. I making phone calls all the time, The update took me about 15 min, after which I tried the Video camera and noticed there was no sound...
Thanks!
well, I noticed that the mic works, but extremely week! I really need to shout in order to hear a whisper... I do this in recording...
I'm starting to believe that maybe it's the mimbrein (Or the piezzo) that is ruined inside the mic...
Is it possible to control the gain in software? (Is there still a chance that the S.W upgrade caused this?)
hi all,
i am currently using defy with the leaked GB 2.3.4.-134 from previously 2.2.1-155. which is my favorite froyo build to upgrade due to (for me) its best battery life conpared to 179
all is working good but i have one issue with this, the in call volume is way too low even when i max out the volume settings anx use the brightest voice quality option. I have read around and this seems to be somewhat common accross models that upgrades into Gingerbread, not limited to defy only. Nobody has posted about it in the forum, so am i the only ones experiencing this? all other sounds is loud enough, just the incall volume, i recall my froyo have an e,xcellent in-call volume.
at first i thought itwas the greenbread mod for the camera ( which render my live wallpaper to FC ) but after i reflash 155, then GB 134, the probkem was there prior me installing the greenbread moxd.
then tried CM7 rc1v2 and the problem remains. no mention about that on the CM7 Forum as well.
any help for the problem guys?
an update,
look into some forums an decided to purcahse an app called volume+(can i mentioned an paid app here for non commercial reasons?) and doesnt do anything to my problem, still no change to the in call volume.
Don't know about GB, but you should have no volume problem w CM7.
Just make sure that you do a factory reset from STOCK recovery before flashing your 155 Froyo.
I did a full sbf flash on all of my froyo with a stock recovery wipe prior to it. so what I did was full wipe, flash 155 frying, root, install 2nd unit, and then install either cm7 or 134 via 2nd unit recovery. The problems exist in both, but when I am in 155, in call volume is loud. I am having serious trouble pinpointing the source of the problem and have yet find any fix.
Try Audio Manager pro. It's a paid app though, but you can see all the volumes controls your phone has to offer and adjust them accodingly.
Calls worked until I installed cm10.1 nightly. Now I can't be heard unless i turn on speaker phone. Sound is still crap but at least I can make a call.
I have tried a few nightly's and now I'm on the people's rom 3.14. (Loving tpr by the way). I doubt it is a hardware issue based on other reports and the fact it was fine until the custom roms.
I still use my phone as a phone from time to time and need it to work or I have to go back to stock.
Thanks
Could have been a bad flash / download
Did you check the md5sum?
leftcranium said:
Calls worked until I installed cm10.1 nightly. Now I can't be heard unless i turn on speaker phone. Sound is still crap but at least I can make a call.
I have tried a few nightly's and now I'm on the people's rom 3.14. (Loving tpr by the way). I doubt it is a hardware issue based on other reports and the fact it was fine until the custom roms.
I still use my phone as a phone from time to time and need it to work or I have to go back to stock.
Thanks
Click to expand...
Click to collapse
Let me make sure I'm understanding you correctly:
Your mic was working fine until you flashed the CM10.1 nightly. Afterwards, the other person could only hear you when you were on speakerphone.
You switched to TPR 3.14. This switch did not fix the mic problem.
You're thinking that switching back to stock (presumably unrooted) will fix this issue.
Please correct me if any of the above is incorrect.
If he issue isn't hardware-related, I'd bet it has to do with the kernel. Let me ask you the following:
Which CM10.1 nightly did you install? Did you see any other issues in the CM10.1 thread which might indicate problems with the nightly you flashed?
What kernel did you use while on CM10.1? I know that the newer kernels (3.4.y verses the old 3.0.y) have had issues and are just recently getting stable.
As CNexus asked,did you check the md5sum for the TPR Rom you flashed?
When you flashed TPR, did you do a full system wipe, or only a Factory Reset (data) wipe? I believe since you were coming from a 4.2.2 Rom (CM 10.1) to a 4.1.2 Rom (TPR), you should do a full system wipe. Some remnants of the CM10.1 kernel/system files could still be there, messing up the mic.
I would think re-flashing TPR (after checking the md5sum) with a full system wipe would fix your issue, but answering these questions would help us diagnose the problem better.
topherk said:
Let me make sure I'm understanding you correctly:
Your mic was working fine until you flashed the CM10.1 nightly. Afterwards, the other person could only hear you when you were on speakerphone.
You switched to TPR 3.14. This switch did not fix the mic problem.
You're thinking that switching back to stock (presumably unrooted) will fix this issue.
Please correct me if any of the above is incorrect.
If he issue isn't hardware-related, I'd bet it has to do with the kernel. Let me ask you the following:
Which CM10.1 nightly did you install? Did you see any other issues in the CM10.1 thread which might indicate problems with the nightly you flashed?
What kernel did you use while on CM10.1? I know that the newer kernels (3.4.y verses the old 3.0.y) have had issues and are just recently getting stable.
As CNexus asked,did you check the md5sum for the TPR Rom you flashed?
When you flashed TPR, did you do a full system wipe, or only a Factory Reset (data) wipe? I believe since you were coming from a 4.2.2 Rom (CM 10.1) to a 4.1.2 Rom (TPR), you should do a full system wipe. Some remnants of the CM10.1 kernel/system files could still be there, messing up the mic.
I would think re-flashing TPR (after checking the md5sum) with a full system wipe would fix your issue, but answering these questions would help us diagnose the problem better.
Click to expand...
Click to collapse
I think you have the symptoms correct.
I did a data wipe but not a factory reset before each rom install.
I started with this rom
cm-10.1-20130303-NIGHTLY-d2spr.zip
I tried 3/13, 3/24 and 3/27 before trying TPR3.14.
leftcranium said:
I think you have the symptoms correct.
I did a data wipe but not a factory reset before each rom install.
I started with this rom
cm-10.1-20130303-NIGHTLY-d2spr.zip
I tried 3/13, 3/24 and 3/27 before trying TPR3.14.
Click to expand...
Click to collapse
Yeah, a full system wipe might be the ticket. Let us know if that works.
I'm Back Baby
I tried a system wipe and a rooted stock rom. This didn't work. I then tried the LJ7_Stock_with_count_reset16 rom and my sound was ok. I cleaned out the mic hole with a pin and bam sound was like normal. I'm now back on TPRGS3.14 and everything is good. I think I had 2 issues but possibly only 1. messed up mic from multiple flashes and crap in the mic hole. I guess checking for a physical problem even as small as a mic debris is an easy first step.
thanks for the suggestions
I'm losing my radio when I flash the newest or any Evervolv nightly. I'm not sure what's going on. However, when I go back to a previous ROM that was working, (Bleu Mynt) I don't have a radio there either. The only way I can have my radio is to restore a nandroid from a previous ROM. I thought flashing the Blackdome kernel would fix the issue, but when I flash the kernel my phone accepts it but doesn't load. The screen goes black. The only thing responsive are my my four buttons at the bottom ( Home, menu, back, and search). When I touch them they light up and vibrate, but nothing else. Also, when i first flashed the Evervolv nightly it said I has mismatched iud and that I needed to wipe my data and reboot. I did that and used fix permissions in my recovery. It said permissions fixed. However, upon reboot, I still had no data connection. Is there something else I need to flash with the nightly? I've been working and researching this for almost 18 hours. I need some help please. Can somebody tell me what's going on and tell me what I need to research in order to fix this issue? Thank you for taking the time to read about my problem.
TheEvoNoob said:
I'm losing my radio when I flash the newest or any Evervolv nightly. I'm not sure what's going on. However, when I go back to a previous ROM that was working, (Bleu Mynt) I don't have a radio there either. The only way I can have my radio is to restore a nandroid from a previous ROM. I thought flashing the Blackdome kernel would fix the issue, but when I flash the kernel my phone accepts it but doesn't load. The screen goes black. The only thing responsive are my my four buttons at the bottom ( Home, menu, back, and search). When I touch them they light up and vibrate, but nothing else. Also, when i first flashed the Evervolv nightly it said I has mismatched iud and that I needed to wipe my data and reboot. I did that and used fix permissions in my recovery. It said permissions fixed. However, upon reboot, I still had no data connection. Is there something else I need to flash with the nightly? I've been working and researching this for almost 18 hours. I need some help please. Can somebody tell me what's going on and tell me what I need to research in order to fix this issue? Thank you for taking the time to read about my problem.
Click to expand...
Click to collapse
Heres some new radios,so when you flash a new rom,you will have this for backup: http://forum.xda-developers.com/showthread.php?t=715485 ,also try a different nightly or a stable version,this one might have caused a bug,fixing another one,thats why its a nightly.
I have the most recent version of PH's blazer rom, v2.3 and have run into a bug/issue that I hope someone else has a solution to! After doing a full wipe and install of the rom everything works great, until I try to switch from the crappy samsung keyboard to the Android keyboard. The phone will completely freeze up and require a long hold down on the power button or a battery pull, but unfortunately after that the phone does not boot all the way, gets stuck at the glowing samsung screen. The only solution i've found is to:
A.) Wipe and reinstall rom after selecting the messed up keyboard input and
B.) Avoid switching to the android keyboard!
I was able to switch to swype just fine and I hadn't re-downloaded swiftkey to make sure it will switch too but I don't have any doubt that it will switch fine. A few more bits of info, I have tried downloading the rom three times thinking maybe a bad download, the md5 checks fine and all 3 downloads gave me the same result.
Am I missing something idiotic or can anyone else replicate this problem?