yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Android Development] highlandsun:
Unless you have evidence (from running a stock kernel) that what you're seeing is caused by the audio routing kernel patches or user libraries, none of this discussion belongs in this thread. Go away.

Don't come back to this thread unless you have evidence that it's relevant.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Well I guess I'd prefer to you start with triaging.

On a clean FRX06 install does this issue exist? You say it doesn't, but I'd like you to verify.

If the issue goes away, then I'd say you implemented some of these fixes improperly - because I have the same device as you on the same network, and do not have this problem.
[Touch Pro2, Tilt 2 Android Development] JustusIV:
Look if I didn't think it was relevant i wouldn't have posted. It sounds completely idiotic to go post something elsewhere saying that, "Yeah I applied this patch and am now having issues" in any thread but the patch thread. If I had experienced this issue anytime besides after your patch I wouldn't have said anything. Besides where this information was posted is called a forum. Its a place where people discuss things. If you don't want people communicating about what you posted, then a forum is probably not the place you should have posted it.

I would be more then happy to verify.

You have always been very helpful. Thanks for not being an a-hole.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
The topic of this thread is very specific. If you can't read and follow directions, perhaps you should not be writing anything in public, you should be back in grade school.

I specifically want people communicating about what was posted, and nothing else. Whatever you're talking about has nothing to do with this. Nothing that was changed in this code has any relevance to how the phone receives calls. You're off topic and derailing the thread. That makes you the asshole here, and you owe everyone else an apology for being so inconsiderate.
[Touch Pro2, Tilt 2 Android Development] yelped:
Please calm down everyone. This is not something that is worth making an issue of. The poster, even though it's possibly off-topic, does write correctly, and in a helpful fashion, and the topic still has relevance to this thread.
[Touch Pro2, Tilt 2 Android Development] latinohot:
I too have the same bug with Pandora, mtf makes my bluetooth come on and off and finally just turns it off, with all three kernels, I have been getting a lot of hangs with kernel .24 most than .23 and .19 so i'll have to wait for a better kernel, btw i ended up using ...D1 for bluetooth,

but I much rather have bluetooth than Pandora(for now, anyways)

Sorry arrrghhh for derailing the thread, but thought we should mention the apps that kill bluetooth

also my appologies to HS as this thread was for AUDIO primarely no bluetooth
[Touch Pro2, Tilt 2 Android Development] Entropy512:
What's fx06? Do you mean FRX06?

Try using stock FRX06. Also, do it with your phone in the exact same location.

Your carrier may simply be hosed and not always passing calls through. I've had it happen before with multiple phones and multiple ROMs.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
a) Don't use this on a work phone. I know my office wouldn't be too happy if I missed calls because my phone was running Android when it's a WinMo device lol...

b) This code is not stable and still in the testing phase. There's some new code on jb's tree, that I don't think has been made 'publicly' (as in, binaries) available.

c) I don't have this problem, so perhaps you've missed a step or done something wrong...?
[Touch Pro2, Tilt 2 Android Development] Serren:
I also have the problem where my phone will not ring using these files. I have all sounds and alerts except phone ringing. And I can test play ringers, and the volume is up.

One odd note that I discovered a day ago that may help isolate the bug. I was playing a video or something when in incoming call came in the phone did ring. This was the first and only time I have heard the phone ringing since using these files. So by having the speaker already triggered will allow a call to ring through. Does this mean anything to anyone?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Are you running clean FRX06 on this stuff or hyc's stuff?

Cuz we've had many conversations on hyc's build...

Either way, you're the only one that seems to have this issue. I've been running this new audio routing code since this stuff was made public, and I've never had that problem.
[Touch Pro2, Tilt 2 Android Development] Serren:
Yeah, its HYC's stuff. He still has the best build around, despite my personal issue. I was just hoping that because the ringer did ring while in a Media mode might shed some light for a dev. on what is going on with audio issues in general I guess.

In case others do have audio routing problems with Froyo, get some media playing and then test if your phone behaves differently.

I've just gotten used to not having a ringer for the sake of speed and stability. Which is huge props to HYC's coding skills. He know how to make things just work. :-)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Well you still haven't triage'd it properly then.

Apply the audio routing stuff on a clean FRX06 build. Then you'll know if your ringer problem is hyc's build or this audio routing code. You're mixing 15,000 things together, and saying you pinpointed the issue to this audio routing stuff is ludicrous. Do your due diligence.
[Touch Pro2, Tilt 2 Android Development] Serren:
I did apply the audio routing stuff on a clean FRX06 build. I had zero audio problems when using a stock FRX06 with just the patches in this thread. But then I had the super slow wakes and the normal random crashes.

I figured HYC included Jerome's new-at-the-time audio code into his personal build since the sound clarity and BT seem the same on his build as they do on FRX06 to me. That is why I follow this thread.

I have my little issue on a 100% pure hyc build. So nothing at all has been mixed. I don't know if I pinpointed the issue to anything, but I did find it odd that if the phone rings while watching a recorded video, it will ring, otherwise it will not. Maybe I'll start a new thread...
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Dude.... hyc does not support his build. Do not create a thread asking for help on his build. Wait patiently for the next official build, or deal with the issues.

If the ringtones work on stock FRX06 with just the audio routing magic added, then there's nothing wrong with the audio routing... which makes me wonder why the hell you're posting in this thread at all.
[Touch Pro2, Tilt 2 Android Development] Serren:
I am not going to ask hyc for help, or you. I never even said that. And I am dealing with any and all issues just fine actually.

I would not have posted and forced you to respond if another annoying user didnt mention a similar audio issue, which was the result of using the files in this thread. I was asking that stupid user to check his sounds and to see if they worked while playing a media file. But what do we now anyway...
[Touch Pro2, Tilt 2 Android Development] slickdaddy96:
Just an FYI Serren, I am using hyc's build, and after reboot and getting 2-3 phone calls or several hours go by I won't get ringtones playing in his build either. It will vibrate(which is a workaround) and it will play the tones when previewing. It will play all notification and alarm sounds just won't ring. I even completely formatted the sd card started from scratch with his build stuff and while it is faster now after the format I still have the same problem.

BIG CAVEAT here though to arrrghhh before he jumps down my throat, I am not asking for help on this issue. Hyc's build is the best and I will deal with the problems that may plague my phone due to running it. I am just simply telling Serren that I have the same issue and I started from scratch with his build again and still had the same problem. I do believe it has something to do with the audio patches(that is just my hunch), but I am not going back to FRX06, so I will deal until FRX07.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
As arrrghhh mentioned, there's a new version of the audio patches, including support for the mic+speakerphone combo. We'll see how it goes soon...
[Touch Pro2, Tilt 2 Android Development] latinohot:
Don't do this, unless...

...you want audio and bluetooth working flawlesly.

AND IF YOU DO IT YOU WILL BE DOING IT AT YOUR OWN RISK.

I have mixed zimage and modules from .24 and .19

more specific i have the modules from .24

and the zimage from .19

and my audio is now superb,

my bluetooth connects faster than ever, the screen comes on fast and have not had a failed wake yet. I have this set up running about 48 hours now

and everything is running as if it was native to the Tilt2, this is awesome for me at least

SO ONCE AGAING IF YOU DO IT, YOU'LL BE DOING IT AT YOUR OWN RISK.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
WTF are you talking about...

People, please don't listen to this... Mixing the kernel (zImage) and the kernel modules (modules-xxxx.tar.gz) is never recommended, and will just end up breaking things like wifi. It will have absolutely no effect on BT or audio routing quality et al.
[Touch Pro2, Tilt 2 Android Development] latinohot:
Hence the f&^% warning

btw my wifi is working better than it did before, and don't tell people what they can and can't do, the warning is clearly stated

DO IT AT YOUR OWN RISK
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
lol. Enjoy your sugar pill, placebo's are fun.
[Touch Pro2, Tilt 2 Android Development] latinohot:
indeed:D

when can we see all of this on a new build?

not my mess of kernels, i mean

but the rest of the developments that have made progress around this parks
[Touch Pro2, Tilt 2 Android Development] highlandsun:
Your post is pure nonsense. The kernel and modules are tied together. The fact that your current setup works indicates only that you still have the .19 modules installed.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
When it's ready. Audio routing code still isn't done, jb is still working on it (but getting close it seems). I haven't spoke to jb in quite some time, so I have no clue what's left.

There's also a lot of devices to test on before release.
[Touch Pro2, Tilt 2 Android Development] latinohot:
Yes i have .19 modules and .24 zimage

nonsense or not, with your helping guide i was finally able to have bluetooth on my Tilt2, and with aaarrgghhh's help on wifi I too was finally able to have wifi

but with this set up that i have now, it connects faster, the phone responds faster and no longer have issues with tones, failed wakes

it might just be a placebo effect but for the last 50+ hours is been running it has been just a pleasureable expirience on my Tilt2 to run
[Touch Pro2, Tilt 2 Android Development] steveoski111:
AHHHH finally i know that i am not alone. thx for posting this up i was going crazy trying to figure out if it was just me or if i may have borked something up. Good to know that other people are having the same issue and that i am not alone. Will keep watching and waiting as this development is amazing!
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
lol I confirmed the issue for you in the PPCG thread, if you had actually read my response.

Enough OT tho.
[Touch Pro2, Tilt 2 Android Development] championc:
I am using the latest Kernel and Modules - htc-msm-linux @ 20110627_223755 and then rootfs.img - 20110516-2d0bb0f. From what I can tell, all I needed to do was to copy the CSV files to the SD Card root, edit the init.froyo.rc file and copy the BCM4325.hcd to the /system/etc folder. It appeared to me that the patch and the libaudio files were all already in place.

Of course, I'm posting this because I'm getting nothing. In the Wireless & Networks section, Bluetooth just will not turn on, on my RHOD100. The necessary changes in init.rc are all there (after phone reboot, I just copied the file off onto my PC and checked).

I have also turned OFF Bluetooth in Winmo and I've now also decided to put on Airline mode too for good measure but still the BT will not turn on. I have also interchanged the BCM D0 and D1 files but still no joy.

Any suggestions ?

C
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Won't work with autobuild kernels.

Either wait for the next release, or use the kernels in the first post.
[Touch Pro2, Tilt 2 Android Development] arpruss:
I can't figure out from this thread whether the new audio routing is supposed to work with the 3.5mm jack or only with Bluetooth and the USB-based 3.5mm adapter?

Thanks!
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
extUSB has been supported for quite some time.

This thread has nothing to do with the 3.5mm jack, whatsoever.

The new audio routing code applies to how the kernel communicates with userland. The "old" audio routing code was a kernel hack, and AFAIK there was little to no feedback from userland on what state the audio should be in. Hence why flipping speakerphone on/off would quite often fix incall audio issues.

BT is a 2-part issue, the audio routing and the firmware. This thread happens to address both, but they're mutually exclusive issues.
[Touch Pro2, Tilt 2 Android Development] Starfox:
Bluetooth will work with the latest autobuild root and kernel. I believe I posted the required changes needed to froyo.user.conf to my little thread.

-- Starfox
[Touch Pro2, Tilt 2 Android Development] championc:
Is the latest rootfs.img - 20110516-2d0bb0f ? Although Battery life is much better, I've lost my data connection and wi-fi is not working either - although maybe this is why battery is better

And also, just to confirm, I assume that the chmod lines do NOT need a "0" before the 666 (since there are other lines with chmod 0666 ....)

C
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
You need to follow the post verbatim.

If you're unsure how to do this testing stuff, then maybe you should just wait. Honestly there hasn't been any userland lib updates to this thread, so I would just wait. All the testing on the existing libs has already been done, we know what's wrong.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Re: this post - there's some newer code, someone mentioned they were going to compile it and throw it up here, but I haven't seen it yet. I'll try to collect it myself...

Reason being, emwe fixed 3.5mm jack on the .35 kernel!!! So if you're using this new audio routing code + new .35 kernel, 3.5mm jack works on RHOD400/500 finally! Kudos emwe (and ACL)!!
[Touch Pro2, Tilt 2 Android Development] xanathar:
arrrghhh, sorry, the updated libraries are here:

http://dl.dropbox.com/u/5179008/libaudio_d828744.zip

Note that these did not fix my headset recognition problem with .39. I just tested the .35 kernel you mentioned and I get the same behaviour.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Thanks, gotta check 'em out!

So you can't use 3.5mm jack with the newest .35?

Scratch that, you're using extUSB. emwe said he didn't touch that code yet, sorry...

Edit - xanathar - have you gotten speakerphone to work with these new libs? I just updated my build, and speakerphone mic is still completely dead... IIRC that's the only bug left with the audio routing code, unless there's something else I missed!
[Touch Pro2, Tilt 2 Android Development] nickleby:
Tested and is working fine on my RHOD500 :) Any chances to see this on .27?
[Touch Pro2, Tilt 2 Android Development] pdawg17:
So if I am on FRX06 but with the "new" audio routing files and edits in place do I only have to replace the zImage/modules with the .35 one and do the haret replace/startup.txt edit? Or do I need to remove any of those edits?
[Touch Pro2, Tilt 2 Android Development] [ACL]:
i just posted a link .. check it out.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Nope, you'll be just fine replacing the kernel as usual, and the new haret/offset in startup.txt.

There's also a .27 kernel that doesn't require the new acoustic code - ACL committed it already, so the newest autobuild kernel has it baked in ;).
[Touch Pro2, Tilt 2 Android Development] pdawg17:
When you say it doesn't require the "new acoustic" do you mean the chmods and audio files on the root of the SD card are not needed?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
The "new acoustic" I speak of is basically everything in the first post of this thread. It's a multi-piece solution, and I mean all of it. The userland libs, the csv's, and the kernel code - which in baked into .35...
[Touch Pro2, Tilt 2 Android Development] reckert:
I haven't updated in a little while - been busy with work and life. Just loaded the new .35 kernel here, and I'm seeing the brcm_patchram_plus from post 2 is running 92.5% cpu. Is there a new Blue tooth? or should I replace with the original BT settings?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I don't think there's any new BT stuff... I don't know if .35 plays nice with BT, I haven't tested. Still lots of things broken on .35 my friend.
[Touch Pro2, Tilt 2 Android Development] xanathar:
I tried to compile an updated kernel from jb's branch (first with integrating latest stuff from htc-msm-2.6.27, and then just plain the jb branch), but it seems that something is going wrong. The compiled kernels just hang after the double vibe in haret (no fb console is shown, it hangs at the progress bar). Haret early log seems ok, says "go go go", but there is nothing in ramconsole. .27 kernels are built with htc_msm_android_defconfig, right? I included CONFIG_AMP_TPA2016D2 to the kernel config. I compiled .39 kernels before, and they just worked fine.

Any ideas?
[Touch Pro2, Tilt 2 Android Development] chunnell:
I think I've done everything here, I've run Android on my Touch Pro, TP and TP2 over the years, but never done any hacking like this, so I don't really know if I've done what I'm supposed to do for this BT hack, but we'll see. However, I do not have a clue as to what you mean about "chmod it 755" for the brcm_patch. I have unzipped it to my SD card, where it now sits, unable to do anything because I don't know what do do.
[Touch Pro2, Tilt 2 Android Development] mbellot:
You need to be in a shell and type in the command:

chmod 755 brcm_patch

That "turns on" the execute bit for the brcm_patch file.

If you still don't understand I suggest you stop and do some reading on basic unix/linux commands.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Either adb or thru the terminal.

If this stuff is over your head, I would wait until it's stable and integrated into the build. Thanks.
[Touch Pro2, Tilt 2 Android Development] chunnell:
I downloaded a terminal emulator and typed in the command, however it couldn't find it, so I must need to put this patch in the right location. Where does it need to go?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Well, first off that bin goes in /system/bin.

However, if you're on FRX07 why are you doing the BT stuff? That is only on builds that pre-date BT... basically any build that isn't FRX07 :p.
[Touch Pro2, Tilt 2 Android Development] chunnell:
I was here:

http://forum.ppcgeeks.com/android-tp2-development/145756-build-complete-froyo-bundle-frx07.html

And that had a FAQ here:

http://xdandroid.com/wiki/Faq

That led me to you as the fix. Nowhere did it say that it wouldn't work on FRX07.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Woah... hold on.

I never said this wouldn't work on FRX07. All I said was all the dirty work for BT is already baked into FRX07 - so the second post (which deals exclusively with BT) is completely unnecessary if you're on FRX07... You only want the new audio routing, which is in the first post...
[Touch Pro2, Tilt 2 Android Development] chunnell:
I see. I erased Android and started again. I'll try that.
[Touch Pro2, Tilt 2 Android Development] chunnell:
Please explain "bind mount".
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
mount --bind /path/from /path/to

So...

mount --bind /sdcard/blah.so /system/lib/blah.so

For example.

Again... you might want to wait on this stuff dude. It's not really stable or recommended unless you know what you're getting into.
[Touch Pro2, Tilt 2 Android Development] mgross029:
No Audio until I make a call

Just something to note... I've noticed if I reboot my phone I will not have audio until I initiate a call. I am using the latest or at least I think it is the latest RIL2 and have noticed this on several different kernals including the 1340 from the FRX07 Full Bundle. Still looking into what could be causing this if anyone has any ideas please let me know... Thanks...
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Well there's only a few kernels that support this new audio routing... so your choices there are slim.

Also, this is experimental code. Not stable yet. Don't expect it to work flawlessly.

Sounds like you've already got a workaround... so I'm not sure what else can be done, until JB resurfaces...
[Touch Pro2, Tilt 2 Android Development] mgross029:
Thanks arrrghhh... That was what I thought too, but wasn't sure if anyone else had this and possibly figured something out that I had missed in my reading of the many posts on XDA...
[Touch Pro2, Tilt 2 Android Development] mgross029:
Audio Routing Better after WM Cab Install

After I went into WM and installed the CAB files that vzihome has posted from PPCGEEKS my audio now routes from the initial start of Android.

Just thought I would share this info with everyone...

http://xdaforums.com/showthread.php?t=1218298

Nice find vzihome and all the folks at PPCGEEKS...
[Touch Pro2, Tilt 2 Android Development] AkumaX:
hmmm... i thought a2dp didn't work unless i installed the files in this thread?

using the 7/27 rootfs, 8/9 kernel and FRX07, i got a2dp right off the bat!
[Touch Pro2, Tilt 2 Android Development] anish88:
are you still having the static from the speakerphone when you make an outgoing call too? maybe i need to change the rootfs?
[Touch Pro2, Tilt 2 Android Development] highlandsun:
To verify your install, get a logcat starting from system boot. The beginning of the log should have this: http://pastebin.com/9rWGsPK2

You should see it successfully open a few .csv files.
[Touch Pro2, Tilt 2 Android Development] xanathar:
On boot, I can see that chmod cannot find /dev/htc-acoustic_wince and /dev/tpa2016d2. Logcat shows this:
[Touch Pro2, Tilt 2 Android Development] highlandsun:
Hm. Well, that explains part of the problem. The user.conf might be running too early. In fact I added the chmod command to my /init.rc here. Since you'll have to edit init.rc anyway for the bluetooth support, it may be best just to put the chmod there too. If you search the init.rc file for "XDAndroid" you'll see two blocks of chmod commands. Add to either of them.
[Touch Pro2, Tilt 2 Android Development] pdawg17:
Editing init.rc (by editing init.froyo.rc) did not fix audio...I'll come back with a logcat in a bit...
[Touch Pro2, Tilt 2 Android Development] sprevrha:
I had the same issue the other day when I reloaded FRX06. What solved it was a hard reset with data wipe in WinMo - from phone off, both send and hang-up keys pressed, then power-on. After that, all sounds work.
[Touch Pro2, Tilt 2 Android Development] vinceweis:
no sound

I also have no sound except through the ear speaker. I have not been able to edit init.rc yet. Nothing lets me make changes. It's my own noob problem.

I did get the csv files loading.
[Touch Pro2, Tilt 2 Android Development] xanathar:
Thanks, that did the trick. My long-standing problem of unavailable audio on some boots seems to be solved, too. Thank you!
[Touch Pro2, Tilt 2 Android Development] AkumaX:
I have this problem too. Maybe a permanent fix in the works/merge into repo?
[Touch Pro2, Tilt 2 Android Development] Serren:
Stupid noob question, but how do I get me changes to init.rc to stick? I'm unable to modify /init.cfg/init.froyo.rc as it is locked. Is there an app or do I have to you adb?