yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
adb is the easiest way... you have to remount / as rw.

mount -o remount,rw /

FYI, bind mounts didn't seem to work at all for me. I adb push'ed everything... and it's working now. I haz BT :D
[Touch Pro2, Tilt 2 Android Development] pdawg17:
*.csv's still at root of SD though right?
[Touch Pro2, Tilt 2 Android Development] ReeS86:
No audio for system sounds

Hey I've carefully gone through all of the set-up for post 1 and post 2 and I don't seem to have any sound on my phone for music, notification, ringtones, etc... I do however have in call audio working just fine.

Bluetooth also will not turn on from the settings menu.

I've made the changes directly to /etc/init.rc by copying in to my computer using QtADB, editing, and copying back, then reboot. The lib and BCM files were copied directly to the filesystem using QtADB as well.

Attached logcat and init.rc for reference

My first attempt at a logcat, chopped of the bottom after a bunch of lines like

19:08:54.186 Debug Sensors 1292 Got unknown event type: 3935/62780/530688

-----------------------------

rhod210

running highlandsun's FRX06 with rootfs-hyc-20110424-495424d.img & system-hyc-20110425.ext2

kernel-01319
[Touch Pro2, Tilt 2 Android Development] Serren:
Just to confirm, since I've never used push before...

I make a copy of /init.cfg/init.froyo.rc

Edit my offline copy with all the changes

using adb and push, overwrite the original with my modded version (this is what the remount does correct?)

Do I need to remount as read only after? Or just reboot?

Thanks arrggghhh..
[Touch Pro2, Tilt 2 Android Development] manekineko:
Okay, I did it on GRX with bind mounts, and ended up with the same problems you had originally. I'll try again later the non-lazy way and report back.
[Touch Pro2, Tilt 2 Android Development] pdawg17:
Still can't get sound working either although I have the same phone as arrrghhh so I must be doing something wrong...I've doublechecked that init.rc is correct, I have pushed the 3 audio files to /system/lib as well...here is the log but I will mention at the very beginning of the log I get this:

I/HTC Acoustic( 1425): libhtc_acoustic.so version 1.0.1.1.

E/HTC Acoustic( 1425): can't open /dev/htc-acoustic -1

E/AudioHardwareMSM72XX( 1425): Could not set acoustic parameters to share memory: -1

Thanks...
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
adb push != remount. Remount allows you to do the adb push, normally it would prevent it because the file system is read-only (RO).

You pushed the rest of the files too? Seems you're on the old htc-acoustic. Push all the files, don't bind mount or symlink anything...

Edit - This wasn't easy by any means. It won't be this difficult come production-time... so if you guys can't get it don't fret, it'll be a ton easier once it's in the build.

Assuming this makes FRX07 (don't see why it wouldn't), the new build is going to be killer!!
[Touch Pro2, Tilt 2 Android Development] pdawg17:
Ok...getting closer...problem with htc-acoustic is I did not have filesystem read/write when I pushed...as you can see below, that looks fixed...now there is a new error...any ideas?

V/Libacoustic-wince( 1425): Running custom built libhtc_acoustic.so

V/Libacoustic-wince( 1425): Device capabilities :

V/Libacoustic-wince( 1425): - Htc voc cal fields per params : 11

V/Libacoustic-wince( 1425): - Dual mic supported : true

E/Libacoustic-wince( 1425): Error opening dev /dev/tpa2016d2 (fd = 11). Error Permission denied (13)

V/Libacoustic-wince( 1425): - Use TPA2016 Amplifier : false
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Did you put that

chmod 666 /dev/tpa2016d2

in your init.rc?
[Touch Pro2, Tilt 2 Android Development] Serren:
I got everything done properly I think via adb. The only part I am not sure of is the brcm patch. Does this look like it would work: (Im new at this stuff...)

C:\Program Files\Android\android-sdk\platform-tools>adb shell

# su

su

# mkdir /data/tmp

mkdir /data/tmp

# chmod 777 /data/tmp

chmod 777 /data/tmp

# exit

exit

#

# adb push brcm_patchram_plus /data/tmp

adb push brcm_patchram_plus /data/tmp

adb: not found

# exit

exit

C:\Program Files\Android\android-sdk\platform-tools>adb push brcm_patchram_plus

/data/tmp

319 KB/s (10216 bytes in 0.031s)

C:\Program Files\Android\android-sdk\platform-tools>adb shell

# chmod 744 /data/tmp/brcm_patchram_plus

chmod 744 /data/tmp/brcm_patchram_plus

# /data/tmp/brcm_patchram_plus

/data/tmp/brcm_patchram_plus

Read default bdaddr of 00:23:76:6D:93:CF

# chmod 755 /data/tmp

chmod 755 /data/tmp

# exit

exit​

Thanks!
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
brcm patch goes in /system/bin. adb push it here, and chmod it 755.
[Touch Pro2, Tilt 2 Android Development] pdawg17:
Thanks arrrghhh! The problem was that I entered the line in the init.rc exactly as written on the first post...that was not working correctly...once I did separate chmod lines for each it now works great! BT works too! Thanks!
[Touch Pro2, Tilt 2 Android Development] ReeS86:
Sweet, got it working. Didn't realize you need to split the chmod into two lines, so it was only processing the first part. Once that was done I got the audio back. Also didn't chmod or put the brcm_patchram_plus in the correct directory.

my chmod lines look like this:

chmod 666 /dev/htc-acoustic_wince

chmod 666 /dev/tpa2016d2

Tested regular phone call, music, system sounds, blueooth stereo headset with music, and phone call with same headset. All audio worked fine and I was able to answer the phone call with the headset button and change the volume, although the headset buttons won't play/pause/next/previous for music played in the stock android music player.

Thanks guys, this is awesome!
[Touch Pro2, Tilt 2 Android Development] zeb carter:
From what I can follow of this entire thread, Bluetooth is working. Unfortunately, while I understand the need to modify certain files, etc, I'm not sure how to do that.

Would I be presumtuous in assuming all this will make it into the next FRX0_ build?

I can wait for it. BT was the only thing I have been waiting for and I am relatively pleased with the work previous to getting this working.

Thanks to all who have worked on this!
[Touch Pro2, Tilt 2 Android Development] pdawg17:
The BEST thing I like about these changes is that earpiece and speakerphone volumes are MUCH higher now and are crystal clear! No more static and low volumes!
[Touch Pro2, Tilt 2 Android Development] nickleby:
Sound works really good with this change, but I'm having troubles with the Bluetooth...

Edit: Forget it, Solved :D
[Touch Pro2, Tilt 2 Android Development] toadlife:
What model do you have?

The audio routing works grea for me but the bluetooth crashes repeatedly for me.
[Touch Pro2, Tilt 2 Android Development] mbellot:
This is freakin' awesome.

I can confirm working audio (external speaker and earpiece) and bluetooth (file push from XP to TP2). Didn't try file push the other way or audio pairing (I don't have a BT headset).

Using a Rhod400 (CDMA).

Camera seems a bit flaky (some FC, one total failure) in both still and video.

Any idea if this would work in Gingerbread? I loaded up a fresh FRX06 card to play with it, but I really prefer GB for responsiveness.

Amazing work, I can't wait to see it all incorporated into the build.
[Touch Pro2, Tilt 2 Android Development] Serren:
Like this:

C:\Program Files\Android\android-sdk\platform-tools>adb push brcm_patchram_plus /system/bin

639 KB/s (10216 bytes in 0.015s)

C:\Program Files\Android\android-sdk\platform-tools>adb shell

# chmod 755 /system/bin

chmod 755 /system/bin

# exit

exit​

Like this?

I have sound, but still no BT. Any ideas?
[Touch Pro2, Tilt 2 Android Development] highlandsun:
chmod 755 /system/bin/brcm_patchram_plus
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Just curious, did you try both BCM firmware files...?
[Touch Pro2, Tilt 2 Android Development] manekineko:
FYI, again, apologies if this is derailing this thread in any way, but I have now on GRX followed both the audio and Bluetooth instructions without using any bind mounts.

Good news! Audio patch works perfectly from my initial tests. I didn't realize there was anything wrong with our audio quality before, but the audio is startlingly louder now. Ringtones and calls both affected.

Bad news! Bluetooth patch causes a reboot within Android when activating Bluetooth. Again, though, this is totally what I expected given the unfinished state of Bluetooth on GRX.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Yea, music streaming apps the speaker now goes ridiculously loud. Pretty cool :D.
[Touch Pro2, Tilt 2 Android Development] toadlife:
nm.

I started over with the new rootfs, system.ext and new data.img and BT is working now. Something was probably screwed up in either my rootfs or system.
[Touch Pro2, Tilt 2 Android Development] toadlife:
BUG: During a call when speakerphone is active, and audible touch tones are active, dialing a number results in the speaker cutting out. Toggling speaker phone restores the sound. Repeatable on my phone. Turning off audible touch tones prevents the bug from happening.
[Touch Pro2, Tilt 2 Android Development] Tippfehler:
I have tried to change all the things of #1 and #2, but BT-sign is gray.

Maybe my dmesg.txt can show, where I have to search for the error, I did not find my BT-load-problems.

Thanks.
[Touch Pro2, Tilt 2 Android Development] Starfox:
Good news: The newest rootfs has both chmod built-in.

Bad news: The autobuild has not built it yet after 7hrs.

The autobuild seems to be using the RIL2 setup so those bind-mounting older RIL should be careful.

-- Starfox
[Touch Pro2, Tilt 2 Android Development] highlandsun:
People still bind mounting the older ril should STOP IT and switch to ril2.

All of these bind mounts just seem to cause more hassles. Better to just drop them all and update the actual files...
[Touch Pro2, Tilt 2 Android Development] highlandsun:
Was showing Quake to a buddy at dinner tonight. I think I startled the entire restaurant before I turned the volume down...
[Touch Pro2, Tilt 2 Android Development] Starfox:
Easy for you to say as you are capable of cooking your own images. For those not as fortunate, the gitorious changelog is not very friendly when it comes to merging different branches, And when you (hyc) is actively maintaining a separate branch (ril) and a previous commit got lumped into the rootfs, well let's just say the user was to only look at the supposed "changelog" from twitter would have no idea that the ril2 got merged.

BTW I have no problems with bind-mounts. I look at the init scripts and determine where I should place my changes.

-- Starfox
[Touch Pro2, Tilt 2 Android Development] nickleby:
I'm speculating, but I think this may be the cause of the bluetooth not work:

[ 36.694702] init: /init.rc: 196: invalid option '--enable_lpm'

[ 36.709808] init: /init.rc: 196: invalid option '--patchram'

I also get those lines, I don't know if it is misspelled in the init.rc :confused::confused:

Or maybe it is irrelevant and the problem has to do with anything else... :(
[Touch Pro2, Tilt 2 Android Development] toadlife:
It looks like the cause of my blueooth crash may have been something in my data.img. After starting from scratch bluetooth worked fine, but after restoring all of my apps via titanium backup (I only restored apps - not system data) bluetooth started to crash again. I've reset my data again and only restored a few select apps. So far so good. I'll have to restore my apps a few at a time and see what the culprit is.
[Touch Pro2, Tilt 2 Android Development] toadlife:
That's definitely your problem. Can you attach/pastebin your entire /init.rc (or /init.cfg/init.froyo.rc)?
[Touch Pro2, Tilt 2 Android Development] nickleby:
Here's my init.froyo.rc
[Touch Pro2, Tilt 2 Android Development] ReeS86:
Not sure if it's worth noting but I've got a T-Mobile Rhod210 and I'm running the energy ROM for my WM install and the BCM4325D1.hcd file worked for me. Since they're coming from WM, are all of these files generic across the WM roms?
[Touch Pro2, Tilt 2 Android Development] Serren:
Ugh! I figured out my problem! It was a typo in my init.rc file with the hciattach code! How frustrating... But I learned a bunch of new stuff, which is good. :-)

And BT works PERFECT!!!!!! Thanks XDA, and all the developers (and Argghhh) for making this happen. Here in California, its the law that we are hands free. The ticket is now like $300 for being caught. So I can again, use my cars built in system. Yeah!

Good job guys!
[Touch Pro2, Tilt 2 Android Development] Serren:
I've attached my good init.froyo.rc below if anyone wants to try it. I had a typo in mine as well at first. But the attached does work. Make sure to rename it to remove the .txt which was added to make the forum happy.
[Touch Pro2, Tilt 2 Android Development] daknap:
Sound Quality

Been a long time lurker of the tp2 forum so heres my bit of input.

Might not be that major but while the sound has got louder with the audio patch it seems to have gone worse in sound quality similar to WM. When android got sound on tp2 it was a real improvement over WM so i'm wondering if its just me?
[Touch Pro2, Tilt 2 Android Development] daknap:
Audio Guide

For anyone who can't get it working easily, here's a step-by-step to test or how I managed to get it working. Not the best way but simple enough.

1. Download Droid Explorer and Notepad++ and install. Might also need a copy of android sdk for drivers. Fresh install of FRX06 is good too.

2. Copy all .csv files from the /windows directory to the SD card root.

3. Download and copy any of the kernel and module packs from the first post and replace in your haret folder.

4. Run android, plug in to PC and run Droid Explorer.

5. Connect to your device from Droid Explorer and open console.

6. Enter "mount -o remount,rw /" without quotes and enter.

7. Go to /init.cfg/ and copy init.froyo.rc to your PC.

8. Open in Notepad++ and add the lines below to the other chmod lines below the first xdandroid set.

chmod 666 /dev/htc-acoustic_wince

chmod 666 /dev/tpa2016d2

should look similar to this:

# XDAndroid permissions

chmod 666 /dev/htc-acoustic_wince

chmod 666 /dev/tpa2016d2

chmod 0777 /dev/smd0

chmod 0777 /dev/smd1

9. When done save and paste over the original in droid explorer.

9. Copy and paste the contents of libaudio.zip to the /system/lib

10. Restart and that worked for me on rhod100_uk.

I'm still trying bluetooth but thanks to devs anyway.
[Touch Pro2, Tilt 2 Android Development] toadlife:
I think I figured out which app was crashing Bluetooth; Pandora. After restoring Pandora the BT started to blow up again. As soon as I uninstalled it, BT stopped crashing.

Can anyone who has BT working install Pandora and see if your BT starts restarting itself?
[Touch Pro2, Tilt 2 Android Development] nickleby:
I don't know if this time I did the right things, but now the bluetooth works! :)

Also placed this option in the startup.txt just in case... hwbluetooth.force=1

Edit:

OMG bluetooth works extremely fast! I've send a .mp3 file to my pc just in seconds! The speed was like 100-150KB/s!! I'll try the bluetooth audio right now :D
[Touch Pro2, Tilt 2 Android Development] highlandsun:
What, you think this is magic and you can just make **** up? Wtf. Ignore this crap. I already told you all the required elements.
[Touch Pro2, Tilt 2 Android Development] toadlife:
Sounds fine to me.
[Touch Pro2, Tilt 2 Android Development] wmg316:
If we use the andboot folder, do we copy the .csv files into the andboot folder? Or to the root of SD as post #1 says?
[Touch Pro2, Tilt 2 Android Development] Tippfehler:
BT ist working now. Audio and BT-Audio seems to work fine.

But, when I try to pair my SE LiveView, I see flying androids and have to enter the PIN.

---

Edit

SE LiveView is paired now after trying it 20 times, but bluetooth is switching off and on all 3 seconds until I reboot the rhod100.
[Touch Pro2, Tilt 2 Android Development] daknap:
Maybe it is just me then. I might make some kind of a comparison even though this thread seems to be more about getting BT working which I am still trying to test.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
The actual *Topic* of this thread is Audio. BT is *secondary*.
[Touch Pro2, Tilt 2 Android Development] Sk0rPi0:
This guide help me out alot, previous try i screw up using adb it's not very noob friendly. But now the mic works in my apps, sound is great. Thanks & appreciation to everyone involved in making android on the rhodium better and better.
[Touch Pro2, Tilt 2 Android Development] KenNashua:
Still trying to get bluetooth working...logcat shows:

D/BluetoothService( 1354): Bluetooth state 10 -> 11
I/bluedroid( 1354): Starting hciattach daemon
V/BluetoothEventRedirector( 1783): Received android.bluetooth.adapter.action.STATE_CHANGED
E/bluedroid( 1354): bt_enable: Timeout waiting for HCI device to come up
D/BluetoothService( 1354): Bluetooth state 11 -> 10
V/BluetoothEventRedirector( 1783): Received android.bluetooth.adapter.action.STATE_CHANGED

Unsure where to try debugging from here...done all the steps twice.
[Touch Pro2, Tilt 2 Android Development] pdawg17:
Audio is much better and BT is working but I am getting a lot of reboots to WM when the phone is not in use...BT is off and I am not in a call when it happens...anyone else seeing this? Trying to troubleshoot if it is a program running in the background or something else...
[Touch Pro2, Tilt 2 Android Development] rpierce99:
I was having a lot of reboot to WinMo problems also and fixed it by switching off of WisTilt2s test kernel and back on to 1324 from this thread. I thought most of the changes for bluetooth and audo had made it into autobuild so his kernel would be fine, but i was apparently wrong :)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Yea, seems if you're using the new audio stuff, you also need the kernels in this thread! I'm sure when kinks are worked out it'll all get committed, but for now, don't mix things... I had issues with all incoming calls, and it was due to mixing kernels with this build :p.
[Touch Pro2, Tilt 2 Android Development] Serren:
I can confirm the Pandora bug. My BT worked fine, but Pandora kept force closing in the background, even though was not even loaded. I just uninstalled it until we can figure out what is going on. I'll try another streaming audio app and see if they work.
[Touch Pro2, Tilt 2 Android Development] rpierce99:
My reboots to winmo were worse, I couldn't play a single sound (ie. hit the volume up button, click a single thing in a game) it would wait like 2 seconds and then reboot to winmo, it was fun.
[Touch Pro2, Tilt 2 Android Development] pdawg17:
I just realized I've been using the 1323 kernel which seems to be causing people some trouble...trying 1324 now...

UPDATE: Does external mic during phone calls work for you guys? Just noticed that mine does not :(

It does work for google search, etc...just does not work when on speaker with calls...
[Touch Pro2, Tilt 2 Android Development] xcuter:
dumb question but how do you access /windows
[Touch Pro2, Tilt 2 Android Development] nickleby:
Kernel 1324 works OK, although I had 2 SoD since yesterday...And seems to be very unstable with the battery...Sometimes the battery shows 100% and after a second shows like 92%, especially when it is charging...
[Touch Pro2, Tilt 2 Android Development] nickleby:
Can be accessed via the ActiveSync (Windows XP) or WMDC (Windows 7), but it is much easier using Total Commander...

I took the files from my stock .nbh ROM file...
[Touch Pro2, Tilt 2 Android Development] toadlife:
Yeah, mic does not work for me during calls when speakerphone is active. I was using 1324, reverted back to 1319 and it still doesn't work. I was experimenting with replacing audiopara3.csv with audiopara3_TMO.csv since they were different and I have the T-Mobile model, but I'm going to recopy the csv files back from the Windows dir and reboot and see what happens.
[Touch Pro2, Tilt 2 Android Development] toadlife:
Recopied the csv files and the speaker still doesn't work when speakerphone is active during calls. Sounds works when recording video though!

Kernel 1319
[Touch Pro2, Tilt 2 Android Development] pdawg17:
Thanks for checking it out...wasn't sure if it was me or not...
[Touch Pro2, Tilt 2 Android Development] highlandsun:
Was it not obvious that you must use these kernels? Why would I bother uploading specific kernel builds, and telling you that *these kernels contain the audio patches* if you could just use any arbitrary kernel?
[Touch Pro2, Tilt 2 Android Development] pdawg17:
For those of us running the correct kernel but external mic not working on speakerphone phone calls, is there any interest in logs from us or is that not part of the "test" for this kernel?
[Touch Pro2, Tilt 2 Android Development] highlandsun:
Sure, get a logcat -v time and a dmesg. This test involves changes to both the kernel and userland at once, and it's not always clear where the bug is or where it should be fixed.
[Touch Pro2, Tilt 2 Android Development] Tippfehler:
If I try it in my office, sound is perfect.

But today in my car with Motonav (IGO My Way) running, it was not possible, to phone with or without BT-Headset. It is ringing, I accept the call, but then the sound is death. Sound in navi also and I have to reboot. (If it is important: ril2 was disabled.)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
:o

Sorry dude. It didn't occur to me at first, and WisTilt2 wanted me to test a kernel. Makes sense when I stop and think about it, I just forgot I had hacked up that build for this audio routing goodness.

Innocent mistake, not like I went around blaming you for releasing horrible crap or something :p.
[Touch Pro2, Tilt 2 Android Development] pdawg17:
Interesting...this morning I twice tried to pair a BT headset and after entering the PIN the phone got VERY SLUGGISH and continued that way until I forced a reboot...reminds me a lot of what happens when I remove the 3.5mm adapter from my phone...

Would the 'ol logcat -v time and dmesg be best or something else?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Certainly would be better than nothing :p.
[Touch Pro2, Tilt 2 Android Development] pdawg17:
I have attached a logcat and dmesg for the lack of mic during calls on speakerphone...I toggled speakerphone on/off 3-4 times toward the end of the logcat btw...

I will be working on logs for the sluggish BT pairing next :)
[Touch Pro2, Tilt 2 Android Development] toadlife:
Logcat from call with speakerphone....

1) called voice mail "123"

2) Turned speaker phone on

3) left voice message (which didn't work of course)

4) Hung up
[Touch Pro2, Tilt 2 Android Development] Serren:
Lots of hangs, slowness, and general unuseability on the 01324 kernel. Switching to the 01319 for further testing. I'll post my new results later on.
[Touch Pro2, Tilt 2 Android Development] pdawg17:
I'm trying to get logs for my BT "sluggishness" but now I can't get my Plantronics 510 to connect even on a fresh boot...is there any way to completely delete the device? I can't find that option anywhere...will try 1319 kernel in the meantime...

Anyone else having trouble connecting after pairing? I'm trying to troubleshoot if it is my headset going bad...
[Touch Pro2, Tilt 2 Android Development] Serren:
I was having similar issues. Slow connections with my car, sometimes no connection. I've been on the 1319 kernel since this morning and my rhod400 seems much happier.

Before turning BT on or off would cause bad stuff, like basically only a reboot would fix. On 1319, BT turns off instantly with no hiccups.