Hi all, I've been having this issue that the Turbonium "tiny audio" fix no longer works after I flash a rom and I have the "tiny audio" on my telus DHD. I've tried flashing it after i've installed a rom and rebooting it and still no luck. I've tried it with other roms like leedroid, RCMix, and MDJ's. I'm all out of ideas, I do complete a clean wipe in between every rom and seems to me like it's happened recently when i've started using the newer roms. Anyways, this issue is starting to get on my nerves and hoping someone will have an answer, Thanks for your input.
As an update: i've done more research and found some people using the RCmix fixed it by flashing the turbonium fix and then adb pushing CodecDSPID.txt, but no luck for me I've been trying to bare the sound because I'm so happy using MDJ's 2.1+3.0, but i would be complete if i could have this fixed. Anyways, feel free to shout any suggestions, I'm desperate....
The update to CodecDSPID.txt was required for the Kingsdom / Sense 3.0 ROM only. The original TurboniumX fix worked fine for me on the ROMs with the old base.
What exactly are you getting when you try to apply the fix? Same tinny sound or no sound at all?
well, when i try to push the CodecDSPID.txt that you gave to killathenoob, I get no sound at all. When i flash the original turbonium, I get no change (meaning i still get the tiny audio), but as you said the original turboniumX fix worked fine with the old base, it's just suddenly i tried to use Kingdom/Sense 3.0 and MDJ's 3.0 that the turboniumX fix no longer works
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?)
Hello. I have a problem with sound in my kaiser with Android. I tried 2 systems [Cynanogen mod 6 (Froyo) and Myn's Warm Donut], 4 radios (from 1.71 to 1.65) and 2 kernels. Sound never appeared. Why?
what zimage or nbh you using if you are using a older one it might have problems
Did you mean kernel? the newest from this page:
http://it029000.massey.ac.nz/vogue/files/?C=M;O=D
it may be that you have muted the media volume in settings.
No. I don't have any sound. Not only media. When someone calls to me, I cannot hear him too and this person cant hear me too.
Audio issue
I have the same problem. I tried different builds and nothing helps. Any suggestions??
Just a thought, but have you tried flashing a stock rom, then flashing to nand again? Flashing a stock rom clears the entire nand, leaving no possibility of stray bits of data left from custom roms.
I have to say, I get the same thing, but with a slight variation. Sound works for me up until i make at least one call (but could happen before that). Once I make that call, either during the call, or after, the sound is gone. I too had myn's donut, and then frayo, and both times, the exact same problem. I will try to flash the stock rom, and then back to android, but it is a problem that I also share.
This is my first post on xda, so please be nice!
<refresh>.
Mu_aawiyah said:
I have to say, I get the same thing, but with a slight variation. Sound works for me up until i make at least one call (but could happen before that). Once I make that call, either during the call, or after, the sound is gone. I too had myn's donut, and then frayo, and both times, the exact same problem. I will try to flash the stock rom, and then back to android, but it is a problem that I also share.
This is my first post on xda, so please be nice!
Click to expand...
Click to collapse
Yeah, flashed it back to a the most recent stock rom, and then back to andriod.. how works perfectly. Sorry i didnt tell you guys earlier.
I think it was to do with the radio thingy-ma-jig. I flashed it with winmo 6.1 from htc website, and then back again.
Now i'm runnying frayo.
I flashed the newest stock rom from htc site too, then 1.65 radio, but it didn't help :/
Wagierek said:
I flashed the newest stock rom from htc site too, then 1.65 radio, but it didn't help :/
Click to expand...
Click to collapse
That is most likely because you didnt flash it right. take the .nhb from it, plug it into your sd card and flash it from sd. try that.
I'm not stupid. I always flash anything like that-not via CustomRUU-because I have damaged my USB socket and now my Kaiser cannot be recognized by computer.
PS: Today when I booted my Kaiser, next to ANDROID word, I saw "handset status changed to 1". When I rebooted, it didn't show. What's this?
Wagierek said:
I'm not stupid. I always flash anything like that-not via CustomRUU-because I have damaged my USB socket and now my Kaiser cannot be recognized by computer.
PS: Today when I booted my Kaiser, next to ANDROID word, I saw "handset status changed to 1". When I rebooted, it didn't show. What's this?
Click to expand...
Click to collapse
Well, with regards to how I got it fixed (the detailed explanation), i flashed it with a custom winmob rom initially, but surprisingly, the same problem i had with android was happening with the winmob. I could make a call after reboot, but after that call, the sound completely died, and the camera did not work. So i tried to flash with the latest stock rom. I've uploaded the actual roms i used on my public drop box folder here => "i tried posting the link, but because i'm new, it wouldnt allow me...pm me"
I am not a professional on flashing, rather i am a beginner. My tytn 2 is a european T-mobile version. I tried to flash it, it did it half way...then stopped! I tried to do it again, but then it just said "...loading..." and would not go past it. But when i booted to my custom rom, it was still there, but the problems had gone. I guessed that it flashed the radio, and nothing else.
When i then went to android, it worked perfectly.
That was my journey.
I hope that helped... maybe.
Unfortunately, it didn't help.
Any other ideas?
I solved mine by changing radio ROM,but i lost sound and camera in windows,any ROM that fit both android and windows???
What version did you flash?
1.65.14.06
Me too!
I flahsed froyo last night and didn't test after makng calls. I'm having the same issue (lose sound after a phone call). I followed the sticky guide and sim unlocked the radio before flashing (which I think I had already done before). I will try changing radios when I get home to see if this resolves the issue and post my results.
Update: I flashed 1.71.09.01 on my ATT Tilt and this fixed the issue. Now sound and camera work great. Phone runs faster also!
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.
Hey everyone,
So I have been having problems connecting my evo to my bluetooth fm transmitter for my car (I can't post links yet, but it is on amazon, the gogroove flexsmart x2) ever since I switched from cm6.1.2 to miui 12.31. The transmitter was working perfectly, and my phone would pair and connect to it flawlessly, however, when I switched to miui, it didn't work at all. It would just not connect, no matter what I did. So I tried switching kernels around, and none of them worked (I tried about 3 kernels on cyanogen before I switched to miui, and switching didn't cause any issues). So I decided to go back to cyanogen, yet my bluetooth didn't work when I restored to a nandroid backup. Bluetooth still wasn't working. So then I went into clockwork and wiped my data/cache and installed the latest cm6 and bluetooth worked. Excited, I installed all of my applications, got my settings right, and installed a different kernel. When I switched kernels to try out a savage one, my bluetooth wouldn't connect. Nothing would work to bring that back, so I deleted my data/cache again and got it to work. Everything worked fine, but I wanted a different kernel, so I tried putting on snap 7.6, and it won't work anymore. I am not entirely sure what to do. I can re-install cm6 by clearing my data/cache, but I want to know why I can't use any other kernels that worked previously. Any suggestions?
Recently, I posted on cyanogen forums, and someone said to use Calkulin's format all zip as well as clear davlik cache. That didn't wok. I also tried going onto a sense rom and installing a sense kernel which didn't work either. I'm not entirely sure what to do. The thing that bothers me the most, not that I can't be on a different kernel than the stock cm6 one, it is that I don't have the option to change, but I did before.
Thanks so much for any help!
Almost sounds like it may be a hardware problem. Most of the software fixes I would suggest you've already tried with no luck. Keep in mind hardware can fail.
spiicytuna said:
Almost sounds like it may be a hardware problem. Most of the software fixes I would suggest you've already tried with no luck. Keep in mind hardware can fail.
Click to expand...
Click to collapse
I would think that it is a hardware problem, but I am lead to believe it is something dealing with the kernel because when I am on a stock cm6 kernel, it works, but when I change the kernel, it fails.
EDIT: Also, would you recommend maybe unrooting my phone and completely resetting it?
Hi all! I have flashed my phone three times with the Synergy ROM and I've flashed the freedom kernel, and chopsuey kernel numerous more times. But for some reason I can't get my camera to work! I tried to the date fix trick and it didn't work. I tried flashing a camera.zip file I found on another forum that was supposed to wipe the data so I could use it again but it was no good.
The camera stopped working once before I rooted my phone but after I tried the date fix trick it worked again. Ever since then it hasn't work
Please help!
Thank you
What recovery are u using. U should be using amonra. If so are you wiping properly?
Have you ruled out possible hardware failure by maybe nanding back to a back up where the camera was working?
Have u checked the md5s for both synergy and your kernels?
Just a few ideas....good luck
Hey,
That sounds more to me a hardware issue, my dads camera on his evo is all screwed up and is just a broken camera and it works when it wants to, but there is nothing really you can do about it.
Does the front camera work?
and are the kernels compatible with your rom?
Try mikg,3.0, it's a better version of synergy .should take care of your problem.
Thank you for all your input but I think it is a hardware issue. I've flashed energy, synergy, CM7 with different (yet compatible) ROMs on each of them and the camera still doesn't work. I've given up
sounds like hardware. The cam is set into a removeable port. Try taking out the back and remounting the cam.