Develop Bugs

[Q] Please help!!! MIC is breaked after Update...

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?)

Bluetooth problem - need help

Bluetooth problem - need help
Here is my situation. I have a EVO 4G Rooted with rooted 3.29.651.5.
My phone's bluetooth paired perfectly with my car for several months.
Then I installed Vlingo and my bluetooth stopped working with my car. I uninstalled Vlingo and the bluetooth worked only sporadically. Since then I have tried almost everything I can and have searched for weeks to get this to work.
I have tried:
* complete wipe and reinstall of ota rooted rom
* reinstalled Vlingo tested, then unistalled again
* deleted and then restored backups of BrcmBlueToothServices 1.0 and Bluetooth Share 2.2
* deleted BrcmBlueToothServices 1.0 and Bluetooth Share 2.2 then flashed rooted ota rom to get clean copies back again (I hope)
* Unpaired my Evo from my car then paired them again.
* Upgraded to rooted 3.30.651.2n.
* Flashed a new King's Kernel #11 (2.6.32.24-king-hav-OcUv)
I know it is not my car as my wife as the same phone I have. I rooted it and except for the recent kernel change on my phone the only real difference is that I never put Vlingo on her phone. I can pair her phone perfectly with my car and it works great just like mine did before Vlingo.
I'm not an expert, my learning curve was huge to get to root and I have done a lot of reading to try to figure this out.
ANY help would be appreciated! I need my phone to work with my car as I'm on the phone a lot.

The kernels will break bluetooth on the CM builds.
The CM framework has been redone and there are few compatable kernels. Yes kings kernel will work, but not everything. Currently, there is no custom kernel (beside the stock CM kernel in each build) that will work and keep bluetooth working on CM roms

kthejoker20 said:
The kernels will break bluetooth on the CM builds.
The CM framework has been redone and there are few comparable kernels. Yes kings kernel will work, but not everything. Currently, there is no custom kernel (beside the stock CM kernel in each build) that will work and keep bluetooth working on CM roms
Click to expand...
Click to collapse
Thanks You very much for your response. Since my technical level is a little limited let me see if I understand. You are saying that my rooted stock ROM is a Cyanogen Mod Build. That ROMS made using this with stock kernels should work with Bluetooth, but if you use a custom kernel there could be a problem.
If this a correct understanding, the only problem is that I was using the stock kernel that came with the ROM and it was working fine for weeks. Then I installed Vlingo and the problem arose. I then unistalled Vlingo and the problem still persisted. Days later I then switched kernels in an attempt to fix the problem. I have the same problem regardless of which kernel I use.
Do you have a suggestion for a solution? Again, thank you.

bluetooth
nykbob said:
Thanks You very much for your response. Since my technical level is a little limited let me see if I understand. You are saying that my rooted stock ROM is a Cyanogen Mod Build. That ROMS made using this with stock kernels should work with Bluetooth, but if you use a custom kernel there could be a problem.
If this a correct understanding, the only problem is that I was using the stock kernel that came with the ROM and it was working fine for weeks. Then I installed Vlingo and the problem arose. I then unistalled Vlingo and the problem still persisted. Days later I then switched kernels in an attempt to fix the problem. I have the same problem regardless of which kernel I use.
Do you have a suggestion for a solution? Again, thank you.
Click to expand...
Click to collapse
i have the same problem did everything mentioned above, rooted my wife evo and mine my Bluetooth doesn't work on mine hers does, maybe the devs could make a backup flashable zip for Bluetooth and htc syn that would be great

Using rooted file manager, I can get to the bluetooth.apk and BrcmBluetoothServices.apk files. When I click on either one of them I get a message that asks:
"Replace Application
This is a system application. Do you still want to replace it?
All previous user data will be saved."​
Question, If I say "OK" what does it replace with? Maybe replacing these two files will change things for me so I can get my BLuetooth function back again.
Any comments?

Nothing I have done has gotten my bluetooth function back again. I'm desperate. Anyone have any ideas. What is frustrating is that my wife's Evo will work just fine in my car, but mine has not ever since I tried Vlingo.
There must be a way to reinstall bluetooth without having to do a factory reset and start all over again. (And I'm not sure that would do it anyway.)
Anyone with suggestions?

Update: I just flashed the updated stock ROM (New_RUU_Supersonic_3.30.651.3_Deodexed_signed - http://www.4shared.com/file/yLaxLUnJ...RUU_Super.html) from http://forum.xda-developers.com/showthread.php?t=836728.
"So Far - So Good" as my bluetooth suddenly worked again. I have flashed the previous stock 3.30.651.2 ROM and nothing changed. This also comes with a updates stock kernel. So who knows, may be this update fixed the problem. I'm keeping my fingers crossed.
BTW, I forgot to wipe anything when I did this update. All good so far.
Later: It works better but not consistent. I still have problems where after a phone call I have to turn the bluetooth off, then on again to make or receive additional phone calls.

I think i fixed my bluetooth !!!!!!
I THINK I FIXED IT !!!!!!
Wow after over 2 months of searching, learning, and trying everything I could think of (other than unrooting and going stock) I stumbled upon what seems to be a solution.
Here is what I did:
Using ASTRO file manager I opened up the "system" folder then opened the "app" folder. From there I scrolled down to the "BrcmBluetoothServices" file and long clicked it until the "File Options" appeared. Then I selected "Edit" and on the next pop-up I selected "Delete". (I was desperate and was going to delete it and reinstall from scratch).
When I selected Delete, a confirmation box appeared that said something that caught my eye like, "Are you sure you want to delete the update as this will return the file to stock?" (or something like that). WOW, when I heard delete the update I figured that Vlingo may have updated this file causing the problems. So I said yes. The update was deleted.
The BrcmBluetoothServices file remained but evidently it reverted to its original stock format. I noticed that my Evo no longer showed a pairing with my car. So I went to my car and deleted that pairing as well and then re-paired my car and phone.
Success! I have been using it for a day and so far so good. My Evo instantly connects with my car when I turn the car on, and I can make and receive phone calls normally. It has only been one day, but it looks good so far!!!
This did fix the problem. Working now for 2 weeks.

[Q] Can't hear anything when making calls!! HELP!

I probably messed up my phone right when i flashed a radio.img
I honeslty didn't know what I was doing and need major help. I can place calls and calls will go through but i am not hearing anything through the speakers nor can they hear me.
I went back to the toolkit and just flashed everything back to stock but still has the same problems at the moment =(
need help please!

okay, after couple flashes... i can at least hear the others voice but my mic is not working at all. what can fix this issue?

What kind of radio did you flash? One that was for your device, i.e. a gsm radio on a gsm device, or a cdma radio on a verizon device? Maybe it's something simple like lint in the microphone hole. You phone's status connects to your mobile network? Try a recording program to see if its limited to the phone.apk, or if its all microphone input. If not, did you try wiping caches and even a factory reset? Maybe you'd need a reflash of the system.img, if you have not reset it since flashing an (assumed) incorrect radio.

bodh said:
What kind of radio did you flash? One that was for your device, i.e. a gsm radio on a gsm device, or a cdma radio on a verizon device? Maybe it's something simple like lint in the microphone hole. You phone's status connects to your mobile network? Try a recording program to see if its limited to the phone.apk, or if its all microphone input. If not, did you try wiping caches and even a factory reset? Maybe you'd need a reflash of the system.img, if you have not reset it since flashing an (assumed) incorrect radio.
Click to expand...
Click to collapse
I flashed the one specifically for my phone. The verizon Gnex and the radio was for the LTE. I took the radio.img from the verizon samsung galaxy nexus development section as well.
After that I booted it to recovery, did all the steps like wipe cache and dalvik and installed the custom rom, gapps, kernel, and then the radio.
Would that have triggered it?

Are both the custom ROM and radio 4.2.2and for Toro?
Did you clean flash the ROM?
Did you restore apps via titanium?
Does the error happen is you don't have any apps installed?

mrxtokki said:
I probably messed up my phone right when i flashed a radio.img
I honeslty didn't know what I was doing and need major help. I can place calls and calls will go through but i am not hearing anything through the speakers nor can they hear me.
I went back to the toolkit and just flashed everything back to stock but still has the same problems at the moment =(
need help please!
Click to expand...
Click to collapse
I am having intermittent issues where I can't hear anyone nor can I play back videos or music either. It sounds like our issues are similiar. I am on a VZW gnex and I went from stock, unrooted, locked, 4.1.1 to the OTA leaked 4.2.2 and my phone has been crazy ever since. My keyboard will go up and down and up and down randomly, my speakers won't work randomly, and my phone freezes up occasionally. Have you tried flashing the 4.1.1 radios back? So far I haven't went back to 4.1.1, because I don't want to wipe my phone.

grandzu said:
Are both the custom ROM and radio 4.2.2and for Toro?
Did you clean flash the ROM?
Did you restore apps via titanium?
Does the error happen is you don't have any apps installed?
Click to expand...
Click to collapse
The rom and radio was for the 4.2.2 and specifically for the Toro.
I did a clean flash, making sure everything was wiped and formatted before flashing any roms
I did not restore any apps via titanium as i just wanted to have a feel of the custom rom before adding any extra apps.
i believe it may just be the device's problem... i got a re-manufactured GNex from asurion since my original had a huge crack =(
Just to make sure if anything was wrong, i did a Nandroid back up from my original working gnex and transferred everything over to the new GNex asurion sent me. But nothing seemed to fix the problem

dkoon1987 said:
I am having intermittent issues where I can't hear anyone nor can I play back videos or music either. It sounds like our issues are similiar. I am on a VZW gnex and I went from stock, unrooted, locked, 4.1.1 to the OTA leaked 4.2.2 and my phone has been crazy ever since. My keyboard will go up and down and up and down randomly, my speakers won't work randomly, and my phone freezes up occasionally. Have you tried flashing the 4.1.1 radios back? So far I haven't went back to 4.1.1, because I don't want to wipe my phone.
Click to expand...
Click to collapse
I unlocked and rooted my phone first thing I got it from Asurion. When i had received the GNex, it was on 4.1.1 and i was able to make calls and everything was fine until I tried to flash 4.2.2 . I reflashed it back to stock settings of 4.1.1 and that should have fixed and flashed the 4.1.1 radio back. I even went to the length of making a Nandroid back up from my original cracked GNex and flash it over to the new device and that sure did not help the problem as well.
All in all, I called Asurion that my microphone is broken and expected to receive another device by Tuesday. I even asked if they can send me a brand new one since the refurbished was not working as "new". Hopefully I get a brand new one.
Even though I will be getting a new one, i was wondering why or how this could have happened. Software related or was it just the phone itself that just crapped on me

mrxtokki said:
I unlocked and rooted my phone first thing I got it from Asurion. When i had received the GNex, it was on 4.1.1 and i was able to make calls and everything was fine until I tried to flash 4.2.2 . I reflashed it back to stock settings of 4.1.1 and that should have fixed and flashed the 4.1.1 radio back. I even went to the length of making a Nandroid back up from my original cracked GNex and flash it over to the new device and that sure did not help the problem as well.
All in all, I called Asurion that my microphone is broken and expected to receive another device by Tuesday. I even asked if they can send me a brand new one since the refurbished was not working as "new". Hopefully I get a brand new one.
Even though I will be getting a new one, i was wondering why or how this could have happened. Software related or was it just the phone itself that just crapped on me
Click to expand...
Click to collapse
@mrxtokki - Well, in your case it sounds like you are fortunate and have insurance so you're getting a new device, or at least a replacement. However, in case you were wondering, I think I may have found the solution. It appears as though your phone might have a faulty headset jack which causes the speaker and earpiece not to work. There is an app in the PlayStore called SoundAbout, that can disable wiredheadset detection and keeps the phone strictly on speaker and earpiece. This fixed my problem. Here is the thread that I found the solution from:
Here is the thread:
https://community.verizonwireless.com/thread/786886
Hope this helps some other soul like me!

Phone calls not working after new firmware

After upgrading to the FOH3 firmware and then flashing on TWRP and Cyanogenmod 12.1 nightly, my phone worked great for days. One day for no apparent reason I could no longer transmit audio when making phone calls on the default phone app. It will connect, and disconnect if the other party hangs up. My speaker, mic, and 4g are working.
I wiped everything TWRP lets me besides MicroSD.
I tried a firmware double-flash and using clean stock install.
I went as far as T-mobile support can.
I'm looking to see if there is a more comprehensive wipe I can do. Perhaps the error exists in an area TWRP doesn't reach. Please give me any ideas.

Camera frozen on black screen no matter what I do

I've done a lot of digging through the forum and can't find an answer, so forgive me if this is an already-answered question.
I have a T-mobile S4 with a camera stuck on the classic "updating camera firmware" error message with black screen. If I open Snapchat the front facing camera will work, but with a slight delay in projection.
Here's the thing...this has happened on two separate phones now and on both of them it happened about 48 hours after I signed into the phone with my google account. Is it possible there is some kind of malware attached to my google account?
In the newest phone I have done a clean full wipe using TWRP, then Odin-flashed a full firmware package I found here on xda (recovery, OS, modem, kernel). Cache wipe and factory reset immediately after rebooting from Odin mode. Still have problem.
Have switched out known good cameras from other phones, and the phone I'm working on was functioning perfectly until I signed into it with my account. Totally stumped here, and really need some assistance.
Phone is:
M919 logic board in I337 body
Kitkat 4.4.4
Baseband: M919UVUFNH7
Kernel: 3.4.9-6281449, [email protected] #1
Build: KTU84P.M919UVUFOK3
Security software version: MDF v1.0 release 3, VPN v1.4 release 2
If anybody's got some ideas, please let me know!

Ok, no answers yet but plenty of views, so either this is an extremely rare issue that no one knows a solution for, or it's a ridiculously stupid question that everyone knows the answer to. I'm going to try and keep a log of what I'm doing with this phone in case any other rookies need assistance in the future.
So far I've flashed three different versions of stock Kitkat onto the phone....OH3, OK3 and NH7. When I flash OK3 my build number doesn't match my baseband (baseband reads NH7)...not sure what's going on there. Also, if I flash OK3 I lose my wifi....do not have this problem with other versions of firmware. Each flash is done after a full clean wipe with TWRP.
I found a thread that mentions an almost identical camera issue being caused on an M919 that was flashed with Nottache Xposed framework for AT&T phones. The OP said they could fix the issue by wiping the framework off the phone. Since my M919 motherboard is installed in an I337 body, I'm wondering if this is something related to a compatibility issue between T-Mobile and AT&T components. Best lead I've got so far.
Two posts have mentioned a fix. One says he opened Google Edition Camera Photosphere and his problem went away. He was running a different machine than mine so I haven't tried this yet, but I'm doubtful. The other user said they have only been able to solve the cam issue by installing a stock modded kernel by @jovy23. All the links I've found to this kernel are dead now, so no dice there.
I'm gonna put my M919 motherboard into an M919 body, wipe and flash stock rom again and see if somehow that does anything.
As a side note, I started getting "SIM not inserted" errors just before I began flashing different roms, and since the initial flash I've lost my SIM completely. So now I've got no camera, no SIM card being read, and sometimes losing wifi. I need this phone for work, so this is kind of sh*tty.

You cant downgrade once youve updated to OK3. The order would have to have been NH7, OH3 then OK3. It seems like mabey its not flashing correctly. Try a different odin program 3.04 3.07 3.09 are good ones. Flash it twice, untick auto reboot and manually power off and back into download mode and flash again. Dont use adv reboot menu to boot into download or it may not flash correctly. If that doesnt work I'm not sure what else to try. Good Luck

Ok, latest update for future readers...
It seems that lordodin912 is right when he says that flashing to OK3 means you can't flash backwards to a previous baseband/build. I hadn't seen that info anywhere so I didn't know about it. I'm not sure how to go about finding this kind of info on the forum but it would have been nice to know ahead of time. Anyhow...thank you for that information lordodin.
Here's where I'm at now:
-I was originally on NH7 with the camera error and sim card error. Flashed NH7 full stock after doing a full wipe and still had problems.
-Flashed OK3 full stock after full wipe and still had the problems, and also lost wifi capabilites (as in the phone wouldn't turn on wifi at all). At this point the baseband read as NH7 but the build read as OK3. I don't know why.
-Tried flashing OH3 after that (didn't know any better) and it wouldn't take. At this point wifi capabilites returned but still no cam and not reading sim card.
-Flashed OK3 again and wifi returned but still no cam and no sim. A couple hours later I powered the phone off and then back on, and Samsung then notified me of OTA updates. This update notification hadn't appeared before I manually rebooted the phone. I took the updates and now have wifi, sim card is being read, and my camera appears to be functioning properly as well. About 20 minutes or so after the updates are applied, the sim card error returned and told me to restart the phone. I did so and now the phone is reading the sim card again.
Right now my best guess is that when I was on NH7 I had accidentally made some app and update settings changes that prevented me from receiving some of the important OTA updates connected to camera and sim functioning, and this caused incompatibility between certain parts of the firmware that had been updated and others that had not. Trying to flash OH3 failed to solve the issue because I had already flashed OK3 before that and you can't go backwards from OK3. I don't know why the initial OK3 flash failed to fix anything, but I'm guessing the flash just didn't take as well as I thought it did. Flashing OK3 twice in a row seems to have done the trick, I presume because it reset and updated everything so that all firmware was compatible with itself.
I don't know how this could have happened (I try to be very careful about what I freeze and uninstall), but it's the most likely culprit because after flashing the latest firmware manually (twice) and allowing OTA updates my phone returns to proper function. Why OK3 didn't work correctly at first is beyond me....I don't see why it should have taken a few hours or a second reboot for OK3 to begin offering updates but whatever.
I'm doubtful that the camera will continue to work after the next 48 hours, but we'll see. I'll report back in with what happens after a few days go by.

Leaving an update here as I said I would.
For two months the phone has been functioning properly. Camera, sim and wifi have all been good. About one week ago my camera started acting glitchy again and then stopped working. The problem is the same as before- upon opening camera app the screen is black with a message saying "updating camera firmware", then nothing happens. This occurred around the same time I started using google hangouts frequently...don't know if that is related to the issue or not.
Yesterday the phone began showing the error message about sim card not being read, and then today it stopped reading the card altogether.
I repeated the same procedure that seemed to fix these problems two months ago and it hasn't done the trick. Full clean wipe of phone using TWRP, then installation of Chainfire's Autoroot, then flashed OK3 stock firmware twice with battery pulls between installations. Factory reset immediately after install of stock ROM. When connecting to wifi, no OTA updates appear. Camera not functioning, sim card not being read.
Phone shows baseband and build number are matching. I have no ****ing idea what the problem is with this phone. Beyond frustrated.
Anyhow, I'll keep updates going as long as I am working with this thing, maybe it'll help someone later. Anyone knows anything that could help, feel free to chime in.