[FIX] Audiofix. Update as promised

---

[B]
THE FOUR (4) UPDATE.ZIPS BELOW CAN BE FLASHED IN AN ORDER, ON ANY ROM. IF ONE DOES NOT WORK TRY ANOTHER. IT CANT HURT YOU. APPLY THESE AS UPDATE.ZIPS IN NANDROID







ANY OF THESE FIXES WILL WORK WITH ALL 2.1 ROMS********

[B][SIZE="3"]Ok so after 2 weeks of testing and thanks to everyone who helped in the testing. we now have a FINAL Fix for the Audio loss problem.

Im going to make this simple.

Update------------------------
This is the OC kernel #89. it may or may not work for you but the way toast compiled it, it DOES NOT have audio loss. it is a guarantee fix but it may not work you. i reccomend using set cpu and min 245 max 729. this allows the best stepping of the processor. idk what roms this will and wont work with. im just throwing this out to help some people until EVERYONE WITH THE ISSUE CALLS SPRINT AND TELLS THEM.

PICK ONE

ToastOC kernel #89 audio fix.

Here is the second update. it is the kernel pulled straight from the RUU. some people say this works. it is completely untouched. i had certain files included that fixed audio loss but i had to remove them due to some complications. so try this if the other 3 dont work, or you dont want OC.

PICK ONE

2.1RUU kernel audio fix

Disclaimer, i have not tested either one. NANDROID BACK UP. im not responsible for data loss. although this has never happened i need to tell everyone. hope one of these 4 work.

End Update-------------------------------

PICK ONE

AudiofixRC

PICK ONE

AudiofixERIS

IF ONE DIDNT WORK. TRY THE OTHER. IF YOU EXPERIENCE A HANG AT BOOT, PULL THE BATTERY AND POWER IT BACK ON. GIVE IT 15 MIN TO BOOT. NOTHING IN THE PATCHES WILL LOCK UP THE PHONE.

********IF YOU APPLY THIS TO ANY FRESH TOAST ROM YOU WILL LOSE OVERCLOCKING ABILITY AND IT WILL BECOME FRESH 2.0D. IF YOU FLASH THIS OVER DC 2.08 AND UP THEN YOU WILL LOSE DC CONFIG. AND PLEASE UNDERSTAND IF YOU APPLY THESE FIXES TO A PORTED ROM OR ANY ROM THAT HAS MODIFIED RAMDISKS THEN IT WILL BE REPLACED WITH A NORMAL BOOT.IMG.

IF anyone has a speakerphone issue or something weird just post a comment and i know the fix. but i have tried to generalize the zips for everyone.

Thanks to everyone who tested and beared threw the 7+ updates

special thanks to,Zenulator(er) Gbhil, BeyondInferno, Treve, Flipz, Damageless, Darchstar. for their contributions. All these Devs are incredible and they all helped to solve this issue when it only effected a few people. they deserve alot of respect for doing so.

[B]The issue is caused by audio drivers in the kernel not resetting. we do not have the source for .29 kernel so there is no fix. we dont know why this effects some people and not others. cyanogen has worked on the issue and he does not have fix. many other forums have reported this issue with no fix. i chatted with a google engineer and he does not have fix. there is no fix that we know of except replacing the kernel with an older version that works. in this case i have used the ones from the ALPHA RUU from sprint and the eris kernel that was made by flipz. Since the audio drivers do not reset it does not allow anything to read them. so it continues resetting and resetting and this causes the cpu to be pegged by the constant retry and retry.

Thanks for the cred! lol
i'll keep you posted, and thanks a ton man.

Edit: some people (including me) have had this problem since the first 100% (not just the current) 2.1 roms, so if this works it'll be pretty big.

I have a quick question. I removed those 2 files after my flash as I use a 3rd party music player. Is this the reason I have not had this issue? If so, do I need to still download and install these 2 files?

Originally Posted by ElAguila

I have a quick question. I removed those 2 files after my flash as I use a 3rd party music player. Is this the reason I have not had this issue? If so, do I need to still download and install these 2 files?

try it and see what happens. like i said this had minimal testing and everyone has different circumstances.

Wasn't aware of this problem, only had fresh2.0d for a little, guess I'll go ahead and save these just incase another occurs...

I go to install both files and in says uninstall?

So both are on my phone as is, and I have been unable to uninstall them?

Originally Posted by chaos67731

I go to install both files and in says uninstall?

So both are on my phone as is, and I have been unable to uninstall them?

you have to remove the apk's first. Then back out shell and then adb install both packages.

C:\AndroidSDK\tools>adb shell
# su
su
# cd /system/app
cd /system/app
# rm HtcMusic.apk
rm HtcMusic.apk
# rm com.htc.MusicWidget.apk
rm com.htc.MusicWidget.apk
# exit
exit
# exit
exit

C:\AndroidSDK\tools>adb install HtcMusic.apk
1032 KB/s (652781 bytes in 0.617s)
pkg: /data/local/tmp/HtcMusic.apk
Success

C:\AndroidSDK\tools>adb install com.htc.MusicWidget.apk
865 KB/s (259656 bytes in 0.292s)
pkg: /data/local/tmp/com.htc.MusicWidget.apk
Success

Originally Posted by Tipharet

you have to remove the apk's first. Then back out shell and then adb install both packages.

I kept getting error about file not found, i did the following and it worked..

: cd C:\android-sdk-windows\tools
: adb remount
: adb devices *if everything is set up right this should output a serial number*
: adb push HtcMusic.apk /system/app
: adb push com.htc.MusicWidget.apk /system/app

...then followed

C:\AndroidSDK\tools>adb shell
# su
su
# cd /system/app
cd /system/app
# rm HtcMusic.apk
rm HtcMusic.apk
# rm com.htc.MusicWidget.apk
rm com.htc.MusicWidget.apk
# exit
exit
# exit
exit

C:\AndroidSDK\tools>adb install HtcMusic.apk
1032 KB/s (652781 bytes in 0.617s)
pkg: /data/local/tmp/HtcMusic.apk
Success

C:\AndroidSDK\tools>adb install com.htc.MusicWidget.apk
865 KB/s (259656 bytes in 0.292s)
pkg: /data/local/tmp/com.htc.MusicWidget.apk
Success

Any chance of gettin this as a flshable zip?..sorry for the bug.im just not too good with adb and wouldnt like to **** the phone up lol...thanks and sorry

Effing right avalanch! I am installing now!. Thanks very much for the fix. This was the only thing holding me back. I'll report back tonight on whether it works