yashsingh1/xdaforums huggingface dataset:
[Hero CDMA Android Development] askwhy:
Avalaunch -- All your hard work on this issue is greatly appreciated, no matter what works, or doesn't. Please, don't forget that.

Since reports are now trickling in of at least *some* continued issues after the last round of fixes, I thought I should bring back up something that has never (to my knowledge) been seriously discussed as a possible factor.

It was mentioned some days back by natheoni, quoted below, and received no response.

When I saw this happen before my very eyes, I also posted about it, quoted below, and received no response.

So, I wanted to bring this back up now. Could we have a little discussion about the phone's attempts to 'Sync while Talking' or perform similar data use while you are on a phone call, and if that might not be as much or more of a factor than the audio drivers, etc.? As most of you know you cannot use EVDO for data while you are on a phone call. Perhaps something is trying to do just that?

If I am barking up the wrong tree here, I am sorry for any confusion this adds to dealing with this already elusive issue.
[Hero CDMA Android Development] fixxxer2008:
why does first boot hang on the first screen for soo long? im going on 10 minutes here, is this normal? im gonna give it 5 more then im going to restore my nandroid.
[Hero CDMA Android Development] fixxxer2008:
jesus, even flashing a rom doesn't take this long from beginning to end, :mad:
[Hero CDMA Android Development] redram38:
This happened to me when I tried flashing the Eris fix. My phone was on the first screen for almost 30 minutes so I nandroided back and flashed the other fix and it did ok. I am on Damagecontrol's newest ROM without LWP
[Hero CDMA Android Development] redram38:
Are you flashing the Eris boot. That was my problem also.
[Hero CDMA Android Development] fixxxer2008:
nope, the other one as im running fresh 2.1. i just pulled the battery and im restoring as we speak. no offense but this fix shouldn't take this long to boot.
[Hero CDMA Android Development] redram38:
I have never had my sync set to auto and from what I can tell have never had the audio issue where it goes out completely. I have some bluetooth issues where audio will come and go some but have never lost it completely. maybe that is why.
[Hero CDMA Android Development] redram38:
If you are using Fresh Try the Eris one. I used Damage and Eris would not work on mine.
[Hero CDMA Android Development] fixxxer2008:
yeah but the fresh 2.0d rom isn't based off the eris leak? it's based off the sprint leak, correct?
[Hero CDMA Android Development] Diplomat2387:
I tried the Eris fix on Fresh ROM and I still had the issue...Should I try to other fix..?
[Hero CDMA Android Development] killacammiami:
it seemed like it help me !!!! thanks alot i had a problem with 1st fixes damage rom and it helped !! i dont have audio loss i was about to say forget roms thanks to u :)
[Hero CDMA Android Development] killacammiami:
i still have sound problem what am i doing wrong ?? i added it to this rom [ROM](1ST with all recent fixxes built into one rom)DamageR_2.7

when someone calls i answer it and i can hear no1 dont know if they can hear me :( how do i fix this .... i hear i may need to do a dalvik cache wipe ... but when do i do that.. i try to when i have this rom on i get a error am i suppose to do a dalvik wipe after i factory clean my rom ??
[Hero CDMA Android Development] pimix2009:
So I'm running fresh 2.0d and I flash the Eris audio fix and now my app2sd is not working. Is there anyway to fix this?
[Hero CDMA Android Development] Avalaunchmods:
Yes there is a fix for a2sd. Ill try to post up im really busy.

Google sync does not cause the issue. Thanks for thr input though.

Sorry to the people with the problem still. This is incredibly hard problem to fix. Other forums with this problem still have it with no fix.
[Hero CDMA Android Development] Avalaunchmods:
About to ruu.

Pray for this to fix it lol
[Hero CDMA Android Development] dirkyd3rk:
i flashed the eris fix over my latest damage and now idk know but my phone is stuck in sprint boot splash screen, i dont know whats wrong, please help, is this a zip that i flash in recovery
[Hero CDMA Android Development] Avalaunchmods:
Yes its an update.zip. and i flashed over the new dc perfect. Maybe u have a2sd or some other modification
[Hero CDMA Android Development] weedman91:
i also tried to flash over DC rom and it is stuck at the white htc page. am i doing something wrong do i wipe anything before i flash the fix or just flash the zip over DC rom.
[Hero CDMA Android Development] Avalaunchmods:
i just flashed the newest dc 2.07.2 and both update.zips, that i redownloaded from here, worked perfect. took awhile to boot but it has booted twice.

honestly if its a 2.1 rom these update.zips

have

to work as the lib files and boot.img are for 2.1.

idk what the problem could be. maybe a2sd, ext part. something along those lines.
[Hero CDMA Android Development] weedman91:
i did a wipe and than flashed the fix and the phone booted up and the audio didn't go off yet after 5 calls and it usually goes off after two. hopefully it dosnt go off. I didn't want to wipe and loose all my apps though, ill do a nandroid and try again without a wipe hopefully it works.
[Hero CDMA Android Development] dirkyd3rk:
stuck again

TRIED TO FLASH THIS OVER DAMAGE......it happened again..........i dont think i have a2sd because dont you have to manually set that up? im running the damage rom still, and i have ext3 and i dont believe my apps are saving to my sd, maybe they are, how would i che
[Hero CDMA Android Development] Avalaunchmods:
try both updates. and as with a2sd, this does not interfere with A2SD

i dont why i posted earlier that it did but all these updates do is replace the ramdisk and kernel, and some lib files and etc files. so no worries with any extras you all have. i just tested a2sd with this and it works fine.

and to see if its working.

1. On your computer in the Android SDK Tools directory, type adb shell

2. In the adb shell, type ls -l /data

3. Look for the entries app and app-private. The entries should look like the following:

app -> /system/sd/app

app-private -> /system/sd/app-private

If they don't, type /system/bin/a2sd install. This should move your apps to the sd card.

^taken from tkirton thread
[Hero CDMA Android Development] Avalaunchmods:
I RUU'ed

and i still have the problem. sooooo im not too sure why. anybody who has 2 cents to throw in that would be great.
[Hero CDMA Android Development] Avalaunchmods:
and i bricked my phone. hahahaha. great day.

well i will get back to you all as soon as i fix this.
[Hero CDMA Android Development] askwhy:
Well, let's go back to the start and review what we know, and what we don't know. Maybe we can catch something we all missed along the way...we being all of us invested in this issue...

Some Questions:

1. What is the nature of the *core* problem, and what are merely the symptoms?

Audio, well that has obviously been the focus since what we usually seem to notice first is when we make or receive a useless, silent, call. We also know that the phone slows to a crawl, and presumably that the CPU is pegged. One thing I cannot find a clear answer to in this or other threads is -- which is truly the chicken and which is the egg? Does an audio problem cause the CPU to peg, or does the CPU getting pegged cause an audio problem?

Do you, Avalaunch, or anybody else, know exactly what is pegging the CPU? Has a particular process been identified? I can't seem to find mention of any one single thing here in this thread or any other -- some mention of audio drivers, but nothing too specific.

Anyways, lets start at the start. What is actually failing?

2. What survives an RUU?

I know nearly everything *can* be replaced by an RUU, but lets review what we know about what *does* get replaced by the RUU you used. Hey, by the way, which RUU did you use, Avalaunch, a recent test one or an older official one?

3. Is this really happening to other phones?

I am under the impression from what I have read here that this is not isolated to the Hero, but I have never actually read anything anywhere else about it. Lets get some links up to other discussions of this issue in other places if they exist, and see what we can find. I don't have any such links though -- anyone?

What else...? Lets not give up, especially if this problem might exist in the Sprint test RUUs themselves (does it?). Hopefully the Sprint final will be free from this, but can we really count on that? I would rather we understand and fix it ourselves.
[Hero CDMA Android Development] Avalaunchmods:
ok instead of answering one by one im going to tell you what i know.

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.

I recently bricked my phone by RUUing from the 2.1 RUU and the 1.56 RUU. i have fixed the brick by replacing all the partitions manually threw fastboot. which was not fun haha. but anyways im currently adding a new fix to the list which will be the overclock kernel with audio fix. this will of course end the camera from being used but it will add another option. im also going to test some more fixes i have made by changing some lib files and replacing them with lib files that SHOULD NOT force the audio drivers to reset. i will get to this later as i am very busy but if i am correct, then using these lib files on ANY rom will fix the problem.

The only help i could use is for people that do not have the issue tell me if they flashed any ERIS rom and a detailed list of all their software. this includes pri,prl,recovery, and their current rom.

Thanks everyone for all the help. now i have to go because my girlfriend has threatened to break up with me if i dont. :D
[Hero CDMA Android Development] askwhy:
As a career diagnostician, I am just trying to break things down since the issue is clearly more clouded than it first seemed -- sorry for the pun, it just happened.

Ok, so if the closest we can get right now to describing the root cause is just that, shouldn't we still wonder what is the specific trigger, or triggers, if there are more than one? Even if the 'fault' is in the kernel, might the trigger(s) not lie elsewhere, and be important to identify?

So, just to clarify, before you semi-bricked your phone with the 1.56, can I assume it was the test 2.1 RUU (with the .29 kernel) that you posted about when you said that:

It sounds like you do know why -- at least in so much as because the recent RUUs have the .29 kernel, which you consider to be the problem area. Can we absolutely confirm that nobody who has returned to the 1.56 and thereby the old .27 kernel has had this problem carry over? Just making sure...

Again, lets talk more about trigger situations. Suggested methods to force the issue have varied in their effectiveness, none being 100% effective at reproducing the issue, and it continues to seem almost random except for that it can't truly be. We just don't see the real pattern yet.

I am not second guessing you at all, just wanting to put as many heads together as possible. You mention Cyanogen has also worked (unsuccessfully) on the issue...I would love to peek at some of the other discussions and see what has been brought up, and would still love to get some links since I cannot find the threads myself.

Great! You've really put a lot into this issue, and I hope we can all see this one put to rest soon enough. If the lib files (which ones, by the way, from where, changed how?) fix the problem, I will be thrilled, but more than anything I want to understand what exactly is going wrong -- what is the nature of the wrench that was tossed into our gears?

Another thought -- when was the very first sign of this issue? Which phone? Which Forum? Which *specific* kernel? Can we actually even pinpoint where this began?
[Hero CDMA Android Development] fisinen:
Hmmm.... I'm using Fresh 2.0d now its just stuck at the Hero screen... Any ideas of what may have went wrong?
[Hero CDMA Android Development] killacammiami:
wait wait wait wait wait .... i dont want to brick my phone im using fresh 2.0d and i been using it for about 3 days with the audio eris fix i have a cdma hero will my phone brick ?? and if so is there any way to unbrick it .... !!! let me know ill remove this ish right now lol thanks
[Hero CDMA Android Development] Avalaunchmods:
no i bricked with RUU's dont worry its impossible to brick with anything i released.

wow. your name says it all :p lol. anyways once again i will try to answer all the questions.

1.The trigger that causes the issue is the audio drivers not restarting. when your phone sits in sleep after a while the drivers restart. which is why when you put it to sleep for 5-10 min. it will have the issue.

2. you make a good point i need to RUU 1.56 successfully before i can make the assumption that RUU cant help. but here is the issue, the 2.1 RUU includes everything we would have when flashing a 2.1. the issue doesnt lie in any of the other partitions such as /etc /data /radio /recovery /system. only in the /sys partition. the ruu writes over them all so even if i did 1.56 then it would only write over them with older things. and the RUU solution is tooo risky for people. as you can see i bricked. i had to restore partitions manually threw fastbootusb.

3. i have found a pattern. before it wasnt 100% sure. but with the roms flashed and none of my fixes applied then if you play audio, let it be a ringtone or music, then let the phone sit in sleep for 5 -10 min. then it WILL occur.

4. im sorry i will not be able to find the specific area where i found the discussions but search "w/audiotrack" in google, xda, android central. other sites and you will find them. there is also a cached google page of an open discussion where a dev. who seems very very experienced in linux discuss's it with someone. and w/audiotrack is what the logcat reports at the start of the issue.

5.i have found an issue which is kind of related to this but much much less prevalent and didnt stop all audio like us. but the developer attached lib files that people reported fixed the issue. im currently testing lib files that i believe have something to do with the issue specifically. i will tell you how that goes.

anything else? lol. im glad to see someone else interested as much as i am in the issue. thanks for the questions too. it helps me sort my ideas out haha
[Hero CDMA Android Development] danaff37:
you asked, so if it helps, I have never had the issue, I have flashed eris roms (damage v1.0), my prl has constantly stayed up to date, usually within a day or two of release, my pri has been 1.70.003 and never changed, have been running amon-ra 1.6.2 since I rooted, currently running damage 2.07.2, and just a little extra, got my phone only about two months ago (not quite though)
[Hero CDMA Android Development] Avalaunchmods:
thank you very much.

the only differences that i can see are your PRI and date you purchased. other than that we are the same.
[Hero CDMA Android Development] askwhy:
Thanks for the detailed reply, and also for suggesting the search term to pursue (I will check it out)! I don't expect answers for everything, but I sure appreciate your taking the time to respond. Let's keep this going, and see what we can shed some light on.

Under normal circumstances (no audio problem), when does the audio driver need to start/restart besides on boot -- under what conditions would it happen? Does it happen *every* time the phone sleeps and then wakes? Do any applications from HTC, Google, or elsewhere have the ability to restart the driver?

We also know the issue can occur while the phone is fully awake, working one moment and then failing the next, with no sleep period in-between. So, what else might be triggering an 'attempted' re-start of the audio drivers besides the need to come out of sleep?

Along those same lines, when the problem occurs, is the system even attempting a re-start of the driver, or doesn't it get that far? (do we know?)

Could the more aggressive memory/minfree/lowmemkiller settings people are using anymore be killing something that is interacting with the audio driver in a way that (indirectly) causes it to fail?

About reproducing the issue -- to test with your method, does the phone have to go to sleep on its own after playing the audio? Does it have to be played with a particular app? I am still a bit fuzzy on how you are reliably getting it to fail by 'playing audio, then letting the phone sleep', and I would love to do some more experimenting if I could just get it to reliably fail for me.

Thanks again for your replies, Avalaunch, and good luck with the lib files!
[Hero CDMA Android Development] pimix2009:
If i get your message correct. the only Eris rom i've flashed are the ones by Flipz. 2.0b, 2.0b2 and 2.0C then i had to get my pri corrected so i did the getting the msl # and fixing your pri stuff. I had problems with audio and phone restarting itself on all Roms i flashed based on the leak and DarchLengend 5.0 but only this rom didnt restart the phone like the others. After the final audio fix came out I flash Fresh 2.0d with the final audio fix (Eris) all these problems are now gone. Firmware: 2.1-update2(fresh) Baseband: 2.32.40.11.09 Kermel:2.6.29 buid: fresh rom 2.0d Software 2.20.651.1 Pri: flipz_01 Prl: i had 60663 last night ( i think, but for sure its some with a 3 at the end) i updated it last night to 60664
[Hero CDMA Android Development] Avalaunchmods:
from what i understand, the htcpowermanagement in the newer roms turn off everything besides tower polling after 5 min. including drivers unless their being used. we cant take that out so no ideas there.

yes it can happen when the phone is awake and that is where the lib files come in to play. i will explain in more detail later once i find exactly whch ones.

and the method i use for making this happen is 100% with me. right now im testing roms i am making and they have lost audio everytime. it also has been reported by my testers that this is a working way to get the issue.

and good news. i think i found a combination that is working correctly. im doing more testing but i cant lose audio for anything. and im using the newest .29 kernel!!!!! pray for me :D
[Hero CDMA Android Development] askwhy:
Oh, I believe you, but I have not been able to reproduce it regularly, and was hoping to find out exactly what you click and in what order, and at what periods you wait for the phone to sleep -- so I can play around and test some things.

Sounds great!

/prays

/crosses_fingers

/rubs_Buddha_belly
[Hero CDMA Android Development] mikethechap:
I am using FlipZ 2.0d, but also had the issue wit several other roms (ic3ROM, Eloysius,etc). The symptoms: Once with the audio player the player kept going while I was listening to CarTalk, but no sound. Plus, I also had the phone drop out of conversations after 2-4 minutes. Eventually(after several dropped calls) , it seems to quit acting up: i can hold a long phone call.

Among possible related ideas that have been brought up as to what is causing it, I've read suggestions as varied as its prl, mls,Titanium, the audio driver. Personally, my stab in the dark is Google Voice. Is there some way in which Google Voice interfaces with the Sprint that creates this situation? Would it be helpful to create a database? I was thinking about that earlier this week. People could enter the apps that are on their phone, the frequency and type of occurrences, the software they are running, those kinds of things. That might at least give us a vector to track down. I'm sure it sounds stupid. Its just a thought borne of the frustration people have been feeling with this. I truly would like to help. I'll try and get my data later to let you know what I'm running.
[Hero CDMA Android Development] Avalaunchmods:
thank you for the input. i have removed every application in earlier testing including gvoice. at one rom i believe i had about 9 apk's. it worked enough to start up and lose audio lol.

and to update people. i finally created a rom with the newest boot.img from RUU. im also using alot of files from about 3 different roms. its working great the rom itself is not losing audio. now im trieng to get it into an update.zip form but theres alot of files that could be the culprit. ill update asap
[Hero CDMA Android Development] shinma6980:
Hopefully this helps. I've never had the issue. I've only ever flashed DC2.06. I've kept my PRL up to date. My PRI is 1.68_003 - and to my knowledge hasn't changed. I've been using the recovery-RA-heroc-v1.5.2.img since I rooted. I got my phone 2 days after it was released.

Now my fiancee on the otherhand has this issue (and the facebook sync but I think I fixed that). She's at work so I don't know her PRI, but she's got DC2.06 also and her PRL is up to date, same recovery image, but we got her phone in the beginning of December (she's got the "with Google" on the back of her phone). So I'm asking - which fix should I try applying with her phone - the AudioErisFix? Her symptoms are some phone calls will not have audio until she reboots but the big one is that her alarm audio doesn't work. If necessary I can try and get her PRI info later today. She doesn't use BT or the music player but she's a Pandora addict.
[Hero CDMA Android Development] riggsandroid:
Had this issue only with DC2.0.7.2

Tried the eris fix because I had used that previously, but it just locked up my phone at the black htc boot.

I am nandroiding back to DC2.0.6.

I am using RA1.6.2 and all other pertinent information is below in my sig.
[Hero CDMA Android Development] Avalaunchmods:
have you tried RC? try them both. and just so people know. it is not freezing your phone. i tested with all dc's. and 2.0.7.2 did cause worries. but after you flash and reboot, let it load and give it 10 min. if it still doesnt load, pull the battery and turn back on. this fixed it for me.
[Hero CDMA Android Development] riggsandroid:
I already went back to my 2.0.6 version but if I have this issue again, I'll try the battery out and turn it on again. I let it sit for almost 20 minutes while doing something else.

Thanks for the work. It is appreciated here.
[Hero CDMA Android Development] Avalaunchmods:
Testers get ready.
[Hero CDMA Android Development] Avalaunchmods:
bump for testers.
[Hero CDMA Android Development] haxrnick:
I hope this works because the ERIS fix froze my phone at bootscreen.
[Hero CDMA Android Development] Jus10o:
I noticed you said for the ones without audio loss.. I have never had the problem. Here is what iv had on my phone that i can remember.

*1.5c ghbil

pri -stock

*2.1 eris build, i think dc v1.. His first rom that started it all.

prl - 60660 (or what it was in February)

pri - 2.10_002 (when we discovered the problem)

did your fix and went back to

pri - 1.70.003 (the above pri still connected to sprint, i did the fix thinking it was my problem to something, which it wasnt. Something in build.prop was)

updated prl every time

*dc 2.0+ until 2.07.2

Current rom

*fresh toast v1

prl - 60664

pri - 1.70.003

Edit: I flashed 3 of flips radios.. So many numbers i cant remember. But the newest radio gave me baddd signal, so i went to his most current released radio of the desire which was an older radio but it worked way better for me... 2.32.40.11.09

In between all the flashes I might of had 1 or 2 fresh roms but then wiped for dc update.