Related
All,
I've just upgraded from WM5 to WM6 with HTC Home RevROM, which is excellent, however, I have this strange issue.
First, I paired my laptop through Internet Sharing over a Bluetooth PAN - works perfectly.
Second, I paired my Jabra BT2020 earpiece.
As soon as the Jabra was paired, the list of devices under Settings->Bluetooth->Devices was empty. Not even the words "Add new device" is present........
I have checked, and I can still continue to use my laptop through Internet Sharing, and I can also use my Jabra earpiece to take phone calls.
Switching the phone off/on and Soft Resets do not solve this problem. Only a hard reset will solve it - but then of course I have to re-enter everything - which I have done, only to have the problem re-occur, hence it is repeatable.
Has anyone else seen this issue and could help me with a solution. I have searched the forum (and Google) to no avail.
Many thanks,
BrianP6
BrianP6 said:
All,
I've just upgraded from WM5 to WM6 with HTC Home RevROM, which is excellent, however, I have this strange issue.
First, I paired my laptop through Internet Sharing over a Bluetooth PAN - works perfectly.
Second, I paired my Jabra BT2020 earpiece.
As soon as the Jabra was paired, the list of devices under Settings->Bluetooth->Devices was empty. Not even the words "Add new device" is present........
I have checked, and I can still continue to use my laptop through Internet Sharing, and I can also use my Jabra earpiece to take phone calls.
Switching the phone off/on and Soft Resets do not solve this problem. Only a hard reset will solve it - but then of course I have to re-enter everything - which I have done, only to have the problem re-occur, hence it is repeatable.
Has anyone else seen this issue and could help me with a solution. I have searched the forum (and Google) to no avail.
Many thanks,
BrianP6
Click to expand...
Click to collapse
Hey man, Unfortunatly this is a bug with my current kitchen, I believe he is using parts of it for making roms. I'm working to fix it soon in my kitchens.
Peace,
Josh
Thanks for the quick reply Josh,
Do you have any ideas at the moment as to the cause? Is it the number of connections, type of connections....... so that I can avoid the bug cropping up.
Also is there a workaround that you're aware of....
oh, and nice work chef
Cheers,
Bri.
BrianP6 said:
Thanks for the quick reply Josh,
Do you have any ideas at the moment as to the cause? Is it the number of connections, type of connections....... so that I can avoid the bug cropping up.
Also is there a workaround that you're aware of....
oh, and nice work chef
Cheers,
Bri.
Click to expand...
Click to collapse
This bug appears only when 2 or more devices get paired.
I've been trying everything, even abusalza himself suggested some module replacement. i'm working on replacing drivers and certain folders in sys in my kitchen but still nothing yet... so far not yet, but it's fixable, i just gotta figure it out.
Thanks Josh,
I guess you'd know this anyway, but for completeness and for the benefit of the whole forum.........
Even though the paired devices are no longer shown in the Bluetooth Devices window, and you can no-longer use your HTC to pair more devices, then so long as you carefully initiate the pairing from the other device, it will be recognised, PINs will be requested and devices configured appropriately. I have just done:
Audi A4 in car kit
Laptop via Internet sharing
Jabra earpiece
None appear on the Devices window, but all (so far) appear to work perfectly.
Cheers,
Brian.
I have had a similar nagging problem with my Motorola S9 and Hermes 100/Cingular 8525. After a new flash, I can pair the headset and the phone relatively easily. During first pairing, I am *not* prompted for the headset's PIN. Over time, switching between phone and music functions becomes more unreliable. Icons disappear while the headset is in use. Discontinuing a call with the headset results in audio resuming through the external speaker instead of the headset, etc.
Eventually, out of the blue, the headset will fail to pair; and I will receive a prompt to enter the PIN number for the headset. I enter the PIN and the phone refuses to accept that it's the correct PIN. From that point on, I'm screwed until I reflash the phone. It never works properly anymore.
This has happened across multiple ROMS, including some of Josh's that I've tried. It happened again the day before yesterday with one of TAI_Sw's ROMS I'm currently using. In this case the profile in Bluetooth settings appeared to be corrupted. The profile no longer read "Motorola S9". Instead it showed a series of block characters (like unsupported fonts). I was able to delete the profile, and, after multiple resets (hard and soft) the phone finally redetected the headset and we went through the configuration wizard again. It's been mostly working well since then.
Has this happened to anyone else?
austinsmartie said:
Has this happened to anyone else?
Click to expand...
Click to collapse
Yep, I have experienced everything you mentioned at one time or another, even the square characters showing up in the device list.
I have gone all the way back to test Faria R32 ROM. It's amongst the best I've found for A2DP with the S9's along with some of PDACorners early ROM's. The drawback are that it doesn't have the 1% battery increase .dll cooked in and also still exhibits the "numbers for character during a call" bug.
It does have nearly 31 MB of memory free after fresh install though. (using 4MB pagepool - default is 6MB)
austinsmartie said:
I have had a similar nagging problem with my Motorola S9 and Hermes 100/Cingular 8525. After a new flash, I can pair the headset and the phone relatively easily. During first pairing, I am *not* prompted for the headset's PIN. Over time, switching between phone and music functions becomes more unreliable. Icons disappear while the headset is in use. Discontinuing a call with the headset results in audio resuming through the external speaker instead of the headset, etc.
Eventually, out of the blue, the headset will fail to pair; and I will receive a prompt to enter the PIN number for the headset. I enter the PIN and the phone refuses to accept that it's the correct PIN. From that point on, I'm screwed until I reflash the phone. It never works properly anymore.
This has happened across multiple ROMS, including some of Josh's that I've tried. It happened again the day before yesterday with one of TAI_Sw's ROMS I'm currently using. In this case the profile in Bluetooth settings appeared to be corrupted. The profile no longer read "Motorola S9". Instead it showed a series of block characters (like unsupported fonts). I was able to delete the profile, and, after multiple resets (hard and soft) the phone finally redetected the headset and we went through the configuration wizard again. It's been mostly working well since then.
Has this happened to anyone else?
Click to expand...
Click to collapse
It frustrated me enough that I started building my own rom!
I released one version here that I have been running for quite some time with no issues in the bluetooth at all.
I need to tweak it a bit more to make it "polished" but it is very useable and stable. I just wanted to run it for a while to see how it is going to act over a longer duration before I continue to fool with it, and I have been rather busy here lately.
Well, if you have a magic potion, please share with the community. And, by the way, this is the only device I pair to my Hermes; so this may be different from the problem Josh and others have described.
joshkoss said:
Hey man, Unfortunatly this is a bug with my current kitchen, I believe he is using parts of it for making roms. I'm working to fix it soon in my kitchens.
Peace,
Josh
Click to expand...
Click to collapse
i just installed your new v15 color(thanks very much for that release it looks great) and i definitely want to pair 2 devices with the phone. this has worked for me in whichever random wm6 rom i found on the web last year and i have been trying to find the right rom for me this week so my question: is this a random bug, is there a trick to doing it right or am i just plain sol?
Hmmm - doesn't happen on my ROMs...
The suspect things I'd be looking at in SYS are:
Bluetooth
Bth_A2DP
Bth_HID
Try replacing those folders with known good ones and see if the problem still happens...
austinsmartie said:
Well, if you have a magic potion, please share with the community. And, by the way, this is the only device I pair to my Hermes; so this may be different from the problem Josh and others have described.
Click to expand...
Click to collapse
No Magic potion! lol
I basically did what CRCinAU described. (His rom doesn't have the issue, and feels a bit faster than mine. But, I was looking to create "My perfect rom").
But I also replaced files in the redist folder with "bt" in their name, with files from a known working rom (anryl's 20755). Like I said I wanted to run the rom for a while, now I just need to go back and tweak and clean up some things in the rom before I make another release.
summary
stickybud said:
i just installed your new v15 color(thanks very much for that release it looks great) and i definitely want to pair 2 devices with the phone. this has worked for me in whichever random wm6 rom i found on the web last year and i have been trying to find the right rom for me this week so my question: is this a random bug, is there a trick to doing it right or am i just plain sol?
Click to expand...
Click to collapse
it is a really odd issue and seems to only affect the hermes... Here is the deal, Some chefs when porting sys grab the cplmain.dll to get the build number and keep some other items in their kitchen sys for stability purposes... I have noticed in my experience when porting, if the cplmain.dll does not match some other components with the same build number it will cause this issue. usually resist, shell, os, folders have been containing these sensitive items. so in short, if the issue is occuring cplmain.dll in redist folder does not match other components in your sys causign the conflict.
edit, and oh. i've tried replacing all bluetooth which had no effect.
So to fix this, the chef needs to report sys correctly and recook the rom.
All;
I've tried several ROMs (including my stock one for my Tilt 2) and I still can't seem to get my phone to work correctly with my car. The phone will dial, connect for about 2 minutes, then the sound will stop coming from my car and go back to the phone. It still says the call is connected from the car, but no more sound and the phone won't reconnect by telling it to use hands-free. It also takes a good minute or so to kill the connection when I hit end on my car.
Any ideas/tweaks/registry hacks you guys can think of? I looked at the MS site for registry changes and those only messed up the phone My car worked fine with other phones and my phone will work fine with other bluetooth devices (headsets, other cars, computer, etc), its just this unholy union seems to be causing problems. I've tried bitpool changes, profile tweaks, etc to no avail. The car manufacturer says my phone 'should' work, but of course, they won't troubleshoot it...
Thanks!
J
Have the same problem with my volvo carkit. Manual switching off the data connection in con.man. may solve your problem temporaly. Bluetooth on HTC really sucks......
same here with vw premium phone with touch adapter and rns 510 all new but not able to connect with my tp2 all other phones work can somebody produce a solution i am happy to donate for it
Dunno if this helps, but I have a TomTom GO 750 and connect to it with the TP2 for handsfree. Im running stock wm6.5
Most of the time its OK. Occasionally the phone wont allow connections, so I have to disable/re-enable Bluetooth on the phone and all is good.
Also, sometimes, every 25 secs or so there is a beep while on a call. Kinda weird. But acceptable.
Well, at least it's not just me
Is there anyway we can change out bluetooth stacks or 'downgrade' the Bluetooth version through software/registry hack? I don't need any fancy bluetooth features, I would just really like my car to work with it!
I'll try the data connection and see, but you're right, not really a long-term fix. Thanks for the idea, I think I tried everything else and option in the gui...
looking-g said:
same here with vw premium phone with touch adapter and rns 510 all new but not able to connect with my tp2 all other phones work can somebody produce a solution i am happy to donate for it
Click to expand...
Click to collapse
I had this same issue where it wouldn't connect. What it ended up being was mis-matched bluetooth names in the various places. Check your bluetooth configuration as well as any tweak programs that may allow bluetooth tweaks, mine were set differently and freaked my car out.
Had the same issues: connection seems fine, but most of the time no sound at all.
I tried different solutions found on different websites, but for me, this one fixed all my bluetooth issues: http://www.everythingwm.com/forum/moto-q-9c/q9c-and-infiniti-g35x-bluetooth-problem-16833-4.html
I applied the registry settings (not all reg keys mentioned did exist on my phone), re-paired (renault built-in carkit), and bluetooth is working fine now.
Similar Problems on GM
I wonder if we are having problems stemming from the same root cause or multiple root causes.
Regardless, I'm having similar problems on a 2009 GMC Yukon with built in Bluetooth. The phone is connected and rings through the auto, but when I hit the off hook to answer, I get no sound and the caller gets no sound. It appears everything connects and the phone says the call is connected, but no good. Usually if I initiate the call from the phone it will work correctly and sometimes not.
I solve it be deleting the phone from the car and the car from the phone and re-pairing, but it only works well for a short while then it fails again.
I'm hoping someone comes up with a great solution(s).
farhope said:
Have the same problem with my volvo carkit. Manual switching off the data connection in con.man. may solve your problem temporaly. Bluetooth on HTC really sucks......
Click to expand...
Click to collapse
Well I'll be... That is what fixed it! Well, not really a fix as I have to disable my data, but actually makes it usable.
Do you know if there is an app out there for this? NoData, while great, doesn't shut down the connection. There is a donation if someone will write one for me
aert said:
Had the same issues: connection seems fine, but most of the time no sound at all.
I tried different solutions found on different websites, but for me, this one fixed all my bluetooth issues: http://www.everythingwm.com/forum/moto-q-9c/q9c-and-infiniti-g35x-bluetooth-problem-16833-4.html
I applied the registry settings (not all reg keys mentioned did exist on my phone), re-paired (renault built-in carkit), and bluetooth is working fine now.
Click to expand...
Click to collapse
Did you create the missing keys/folders or just make changes to the keys you had?
I'm willing to try anything to not have to disable my data everytime I want my phone to work! Yes, I'm that lazy to expect things to work right the first time
All right! Got it fixed, thanks guys.
1. Modify the HandsFree plug-in:
HKLM\Software\WIDCOMM\Plugin\HandsFree
i. Change SupportedFeatures to 45 (default is 1135)
ii. Add value HFBDA binary, set to same value as LastConnectedBda
iii. Add value HFDeviceType decimal 2
2. Modify the WIDCOMM bluetooth general settings:
HKLM\Software\WIDCOMM\BtConfig\General
i. Change bdaddr to (no value)
ii. Change DisableReopenAudio to 0 (default is 1)
3. Reboot device
I tested it for a few minutes and it was solid and sounded good, no freaky occurances. We should sticky these for other people having BT issues...
Credit to EverythingWM and aert for the pointers!
thats good news loki but some values i can not find in my registry i will try to add them and then give it a go
looking-g said:
thats good news loki but some values i can not find in my registry i will try to add them and then give it a go
Click to expand...
Click to collapse
Yes, I added the missing ones, restarted the phone, re-paired with my car and, so far, works great. I'll give it a week before I start doing the happy dance.
is it possible to make a cab or reg key file for it
I can create a reg for all the keys except the HFBDA key. That should match the LastConnectedBDA key which may be different on our phones. What is yours set to? Mine is 00,1e,ae,20,c2,80. I wouldn't want to have someone import it when the setting isn't right for their particular build/version/etc.
Loki007 said:
All right! Got it fixed, thanks guys.
1. Modify the HandsFree plug-in:
HKLM\Software\WIDCOMM\Plugin\HandsFree
i. Change SupportedFeatures to 45 (default is 1135)
ii. Add value HFBDA binary, set to same value as LastConnectedBda
iii. Add value HFDeviceType decimal 2
2. Modify the WIDCOMM bluetooth general settings:
HKLM\Software\WIDCOMM\BtConfig\General
i. Change bdaddr to (no value)
ii. Change DisableReopenAudio to 0 (default is 1)
3. Reboot device
I tested it for a few minutes and it was solid and sounded good, no freaky occurances. We should sticky these for other people having BT issues...
Credit to EverythingWM and aert for the pointers!
Click to expand...
Click to collapse
Could anyone explain what these settings mean? There is no point of tweakin something if I do not know what each of setting does, well of course it has a point of tweaking it, but I would really like to know what it means. Does anyone has a problem syncing the phonebook after aplying that tweak or it is just me?
Thanks for help!
Can someone explain what all of these REG changes do?? I dont want to end up like before. There was a CAB floating around that was supposed to fix the BT issues and while it made it better it drained my battery VERY VERY quick.
Do these changes have any effect on battery life???
aert said:
Had the same issues: connection seems fine, but most of the time no sound at all.
I tried different solutions found on different websites, but for me, this one fixed all my bluetooth issues: http://www.everythingwm.com/forum/moto-q-9c/q9c-and-infiniti-g35x-bluetooth-problem-16833-4.html
I applied the registry settings (not all reg keys mentioned did exist on my phone), re-paired (renault built-in carkit), and bluetooth is working fine now.
Click to expand...
Click to collapse
WOW.. now when my TP2 rings, I actually get the custom RINGTONE out of my GARMIN NUVI SPEAKERPHONE and it doesnt DROP calls right after the first ring AND I can answer and hangup fine.. the phone book is still a little messed up in that any contact with ONLY a COMPANY NAME and not a first and last name loads as a phone number in the name field...
Does anyone know if any of these REG changes degrade battery life? I am asking because a while back I had a CAB that was supposed to fix the bluetooth and while it improved the paring, it drained my battery live very very fast.
Also can someone explain WHAT these reg changes and additions do? I would really like to know what I am doing to fix the issue...
-- Dave
One more thing, now with the fix, it appears on my garmin, when I press LAST DIALER, LAST RECEIVED or MISSED, I get NO DATA AVAILABLE .. I didnt have this problem before the fix.. Is there a solution??
Thanks....
Loki007 said:
I can create a reg for all the keys except the HFBDA key. That should match the LastConnectedBDA key which may be different on our phones. What is yours set to? Mine is 00,1e,ae,20,c2,80. I wouldn't want to have someone import it when the setting isn't right for their particular build/version/etc.
Click to expand...
Click to collapse
correct; mine is different from that.
also, the bdaddr key keeps resetting itself when I reboot my phone.
I even tried changing the key type to something other than binary, and it still reset itself to binary, and changed back tot he default value.
These hacks did not work at all.
I came across this cab that changes some BT settings, but at least one guy reported it draining the battery very quickly (not enough posts to post links...sheesh):
forum.ppcgeeks.com/showthread.php?t=90155&highlight=bluetooth
This is a testing thread and I hope it works for most.
I or any of the dev's are not responsible for a failure in your device.
Basically, I've been trying to get Bluetooth working properly on my VZ TP2 since hyc's audio routing post with FRX06. The dev's and other great minds (hyc, JB, Stinebd, emwe, Detule, StarFox, arrrghhh, ACL and many others) deserve the credit for getting the components of this puzzle working. All I've done is figured out how to put it together (at least for my Rhod500).
I have used what hyc has posted in his audio routing thread and just found the right combination. I have not changed any of the code in these files.
Since FRX07 I have been able to get a BT headset audio routing working properly by following this workaround. Pairing the headset then disconnecting it. I then would place a call and then reconnect the headset. This would allow audio to route correctly to the headset and it would stay that way until I disconnected the headset.
So since most of the work was done, here is what I did to get the final pieces working. As hyc posted in his audio routing thread under the BT section. He talked about needing the .CSV files from your WM \Windows directory.
These files I found are the Database files which contain the configuration information about each BT device. I've also found there are some existing .CSV files which are part of the FRX07 base build under /system/etc which do not contain as much information as the .CSV which were part of WM.
Also, I have found that the libaudio.so is the main file needed to get the audio to route properly.
So, to get it all working I have copied the files to my SDCARD and did a mount --bind to the existing files within the /system/lib and /system/etc folders in FRX07. After doing this I was able to pair my headset with the phone and make a call. The audio routed correctly to the headset. I also tested if the headset got disconnected if it would route back to the ear piece and it did.
Below is a snippet from my froyo.user.conf file and I have attached my working .CSV files and the libaudio.so file from hyc's audio routing post.
Please test this out to see if it works for you and post your results and many thanks again to all of the dev's who put in a ton of time to get all of this and other things working for our faithful old Rhod's.
Yes, you could just go out and buy a working Android phone but where would be the fun in that?
Put this under the custom shell commands section
Code:
mount --bind /sdcard/libaudio.so /system/lib/libaudio.so
mount --bind /sdcard/AudioPara3.csv /system/etc/AudioPara4.csv
mount --bind /sdcard/AudioPreProcessTable.csv /system/etc/AudioPreProcess.csv
mount --bind /sdcard/AudioFilterTable.csv /system/etc/AudioFilter.csv
As you can see above the WM version of the files are named different than the /system/etc .CSV files. Also, this illustrates that my files are located in the root of the sdcard, so you may need to adjust the statements if you put the files in a different location.
Attached are the .CSV and libaudio.so files I'm using.
Unzip and copy to your sdcard
BTW, I have taken this and recreated it several times using the original FRX07 files just to be sure that it was working properly. Also, you may need to us your .CSV files if mine do not work properly for you. Best of Luck to All!
mgross029 said:
This is a testing thread and I hope it works for most.
I or any of the dev's are not responsible for a failure in your device.
Basically, I've been trying to get Bluetooth working properly on my VZ TP2 since hyc's audio routing post with FRX06. The dev's and other great minds (hyc, JB, Stinebd, emwe, Detule, StarFox, arrrghhh, ACL and many others) deserve the credit for getting the components of this puzzle working. All I've done is figured out how to put it together (at least for my Rhod500).
I have used what hyc has posted in his audio routing thread and just found the right combination. I have not changed any of the code in these files.
Since FRX07 I have been able to get a BT headset audio routing working properly by following this workaround. Pairing the headset then disconnecting it. I then would place a call and then reconnect the headset. This would allow audio to route correctly to the headset and it would stay that way until I disconnected the headset.
So since most of the work was done, here is what I did to get the final pieces working. As hyc posted in his audio routing thread under the BT section. He talked about needing the .CSV files from your WM \Windows directory.
These files I found are the Database files which contain the configuration information about each BT device. I've also found there are some existing .CSV files which are part of the FRX07 base build under /system/etc which do not contain as much information as the .CSV which were part of WM.
Also, I have found that the libaudio.so is the main file needed to get the audio to route properly.
So, to get it all working I have copied the files to my SDCARD and did a mount --bind to the existing files within the /system/lib and /system/etc folders in FRX07. After doing this I was able to pair my headset with the phone and make a call. The audio routed correctly to the headset. I also tested if the headset got disconnected if it would route back to the ear piece and it did.
Below is a snippet from my froyo.user.conf file and I have attached my working .CSV files and the libaudio.so file from hyc's audio routing post.
Please test this out to see if it works for you and post your results and many thanks again to all of the dev's who put in a ton of time to get all of this and other things working for our faithful old Rhod's.
Yes, you could just go out and buy a working Android phone but where would be the fun in that?
Put this under the custom shell commands section
Code:
mount --bind /sdcard/libaudio.so /system/lib/libaudio.so
mount --bind /sdcard/AudioPara3.csv /system/etc/AudioPara4.csv
mount --bind /sdcard/AudioPreProcessTable.csv /system/etc/AudioPreProcess.csv
mount --bind /sdcard/AudioFilterTable.csv /system/etc/AudioFilter.csv
As you can see above the WM version of the files are named different than the /system/etc .CSV files. Also, this illustrates that my files are located in the root of the sdcard, so you may need to adjust the statements if you put the files in a different location.
Attached are the .CSV and libaudio.so files I'm using.
Unzip and copy to your sdcard
BTW, I have taken this and recreated it several times using the original FRX07 files just to be sure that it was working properly. Also, you may need to us your .CSV files if mine do not work properly for you. Best of Luck to All!
Click to expand...
Click to collapse
I'll give this a shot and let you know how it works on my RHOD400.
fishingmedic said:
I'll give this a shot and let you know how it works on my RHOD400.
Click to expand...
Click to collapse
Thanks that would be appreciated...
What kernel are you using?
I like the effort, but I honestly don't see any difference to hyc's thread other than this tip:
mgross029 said:
Since FRX07 I have been able to get a BT headset audio routing working properly by following this workaround. Pairing the headset then disconnecting it. I then would place a call and then reconnect the headset. This would allow audio to route correctly to the headset and it would stay that way until I disconnected the headset.
Click to expand...
Click to collapse
Which I guess could be the key to getting it all to work? I'm just wondering if this step is required to get it all working properly.
Curious, does speakerphone work for you? Have you ever had audio "just die"?
arrrghhh said:
What kernel are you using?
I like the effort, but I honestly don't see any difference to hyc's thread other than this tip:
Which I guess could be the key to getting it all to work? I'm just wondering if this step is required to get it all working properly.
Curious, does speakerphone work for you? Have you ever had audio "just die"?
Click to expand...
Click to collapse
arrrghhh,
I agree it is very similar to what hyc is doing and that was why I put many references to his thread in my post. I also cleared creating the new thread with hyc before I posted. I did this mainly so this post would not get lost in the audio testing thread.
The main difference between this thread than hyc's is that his was in reference to getting BT to work on FRX06 and if you would follow the same procedures as posted there with FRX07 it essentially would not work and cause problems with the phones ability to operate. I found that putting the libhtc_acoustic.so file into FRX07 really made they system unstable.
My Speakerphone does work... Also, I have tried several combinations of items to see if what worked and what did not... I have lost audio in these tests, but so far with what I've posted using the XDAndroid version of FRX07 everything seems to work correctly for my Rhod500...
Thanks for the input / feedback...
Edit: Sorry missed your first question... My specs are posted in my sig... Currently I am running StarFox's 8/20 Test Kernel...
mgross029 said:
arrrghhh,
I agree it is very similar to what hyc is doing and that was why I put many references to his thread in my post. I also cleared creating the new thread with hyc before I posted. I did this mainly so this post would not get lost in the audio testing thread.
The main difference between this thread than hyc's is that his was in reference to getting BT to work on FRX06 and if you would follow the same procedures as posted there with FRX07 it essentially would not work and cause problems with the phones ability to operate. I found that putting the libhtc_acoustic.so file into FRX07 really made they system unstable.
My Speakerphone does work... Also, I have tried several combinations of items to see if what worked and what did not... I have lost audio in these tests, but so far with what I've posted using the XDAndroid version of FRX07 everything seems to work correctly for my Rhod500...
Thanks for the input / feedback...
Edit: Sorry missed your first question... My specs are posted in my sig... Currently I am running StarFox's 8/20 Test Kernel...
Click to expand...
Click to collapse
Starfox's test kernel supports the new audio routing...? I'm running his kernel without the new (userland) routing stuffs.
arrrghhh said:
Starfox's test kernel supports the new audio routing...? I'm running his kernel without the new (userland) routing stuffs.
Click to expand...
Click to collapse
Without JB's libhtc_acoustic, this thread is not in fact testing the "new" audio routing.
detule said:
Without JB's libhtc_acoustic, this thread is not in fact testing the "new" audio routing.
Click to expand...
Click to collapse
Oh, I guess I didn't realize that. Interesting... I ignorantly assumed that this was using the same audio routing from JB.
arrrghhh said:
Starfox's test kernel supports the new audio routing...? I'm running his kernel without the new (userland) routing stuffs.
Click to expand...
Click to collapse
Trust me I am not a developer nor do I play a developer on TV, but I did stay at a Holiday Inn Express before...
All I know is by using the information I posted at the top of the thread I was able to get BT in-call audio routing correctly.
I have used the kernel StarFox had posted which was based off the mainline 1348 kernel and was able to get the BT audio routing to work correctly with that as well.
I put this as testing because I am not sure the result that everyone would have with this.
If anyone has been able to test it out I would appreciate if you could post back to let us know if it has worked correct or not...
Thanks...
mgross029 said:
Trust me I am not a developer nor do I play a developer on TV, but I did stay at a Holiday Inn Express before...
All I know is by using the information I posted at the top of the thread I was able to get BT in-call audio routing correctly.
I have used the kernel StarFox had posted which was based off the mainline 1348 kernel and was able to get the BT audio routing to work correctly with that as well.
I put this as testing because I am not sure the result that everyone would have with this.
If anyone has been able to test it out I would appreciate if you could post back to let us know if it has worked correct or not...
Thanks...
Click to expand...
Click to collapse
Do you still get the static from the speakerphone when placing an outgoing phone call?
anish88 said:
Do you still get the static from the speakerphone when placing an outgoing phone call?
Click to expand...
Click to collapse
Why don't you try it and tell us...
I would assume so since it's not using the new libacoustic code, but I don't know for sure. It's a minor issue to me, flip speakerphone on/off and it's gone.
anish88 said:
Do you still get the static from the speakerphone when placing an outgoing phone call?
Click to expand...
Click to collapse
Yes... Still some static, but not bad... Kind of a minor hisss....
I left myself a VM on my work phone and I do not hear the hiss in the message... It is actually quite clear...
arrrghhh said:
Why don't you try it and tell us...
I would assume so since it's not using the new libacoustic code, but I don't know for sure. It's a minor issue to me, flip speakerphone on/off and it's gone.
Click to expand...
Click to collapse
yeah thats the thing that I do too. ill wait too. everything else is working great though.
Test results on Rhod300
I gave it a try on .27 kernel - yes, it is partially working. What I did differently was instead of using "mount --bind", I rename libaudio.so under /system/lib, and copy the one in your zip file under that directory; then I copy the .csv files under /system/etc (I've tried both your files and the ones from my phone). Here are my test results:
BT turned on fine and pairs with my BT earpiece fine.
Incoming calls got routed to the BT earpiece correctly.
Outgoing calls the audio stays with the phone and cannot be switched (at least I didn't find a way) to BT earpiece. I tried toggling the "Bluetooth" button at the lower left corner of the dialer, and play with connect/disconnect button on the earpiece and non of them helps.
Once the earpiece is disconnected from the phone, there's no way to reconnect it back besides unpair/pair the earpiece again. Toggling BT on/off and even reboot the phone won't help.
Even though it is "half" working, I think it's a big step moving forward. Thanks, mgross029.
Click to expand...
Click to collapse
OK, I thought I messed up your .csv files and the ones from my phone, but I did not. And yes, I renamed the files to match the ones originally under /system/lib and /system/etc directories and changed their permissions. So, the test results still stand at this point. I got a AT&T Tilt2 and the bootloader screen shows Rhod300.
Click to expand...
Click to collapse
Since this is about tests on your efforts, I think it's probably easier for everybody to follow just by moving my post from FRX07 thread to here.
Dinky said:
Since this is about tests on your efforts, I think it's probably easier for everybody to follow just by moving my post from FRX07 thread to here.
Click to expand...
Click to collapse
Thanks Dinky, for posting this over here so others can see your results...
Thanks for the additional feedback... At least it is partially working for you...
Another option if you have the room on your sdcard is to put the original FRX07 bundle on it, create a new data.img or ext4 which every you are using. Then mount --bind the files from your user.conf file just to see if it works correctly. Not a big deal if you cannot do this, but it's something to try if you are able too...
Click to expand...
Click to collapse
Did that. Went directly to BT tests without anything installed/set up after first boot. Exact same result. Earpiece will not reconnect once disconnect. I had to unpair/pair the earpiece again to get it connected again. Are these all working for you? I wonder what differences could it be besides the hardware?
Dinky said:
Did that. Went directly to BT tests without anything installed/set up after first boot. Exact same result. Earpiece will not reconnect once disconnect. I had to unpair/pair the earpiece again to get it connected again. Are these all working for you? I wonder what differences could it be besides the hardware?
Click to expand...
Click to collapse
Occasionally, I have had issues where my headset will not automatically connect to my car and I usually will disable BT on the phone and re-enable and that does the trick. Another item to look into is which BT headset are you using? The configuration for the hardware may not be in the database (CSV)... You could actually take some logs to see what the problem is...
If you have adb running do this...
C:\<directory where adb is located>\adb shell logcat -v time > logcat.txt
From a Terminal window:
logcat -v time > /sdcard/logcat.txt
Try to do your pairing while that is running after you are done with your testing Ctrl-C to break out of it and then go to your adb folder there should be the logcat.txt file... This should show what is happening or not happening when pairing or connecting...
mgross029 said:
Occasionally, I have had issues where my headset will not automatically connect to my car and I usually will disable BT on the phone and re-enable and that does the trick. Another item to look into is which BT headset are you using? The configuration for the hardware may not be in the database (CSV)... You could actually take some logs to see what the problem is...
If you have adb running do this...
C:\<directory where adb is located>\adb shell logcat -v time > logcat.txt
From a Terminal window:
logcat -v time > /sdcard/logcat.txt
Try to do your pairing while that is running after you are done with your testing Ctrl-C to break out of it and then go to your adb folder there should be the logcat.txt file... This should show what is happening or not happening when pairing or connecting...
Click to expand...
Click to collapse
OK, did that. I saw some errors pertaining to the BT connection, but what do they mean is beyond me. It looks like there's a permission problem? I have that portion of the log attached below...
Dinky said:
OK, did that. I saw some errors pertaining to the BT connection, but what do they mean is beyond me. It looks like there's a permission problem? I have that portion of the log attached below...
Click to expand...
Click to collapse
Thanks for the log Dinky...
It looks like rfcomm is timing out before it can fully establish a connection to your BT headset... Which headset are you using? I don't think I remember seeing you post that... Sorry if you already did... I know I did some searching and saw some posts where some headsets do not connect as fast as others and that delay caused the connection to fail.
The only other thing I can think that I may have done that most may have not was to install the volume cab files from vzihomes thread. I know that helped with audio routing on my speaker even before I figured out the BT part. I used to boot into android with no sound and then after adding the cab files to WM audio routes through my speaker at first boot.
Just something to try... Not sure if it has anything do with what you are experiencing though...
JB's libhtc_acoustic.so
Just out of curiosity and the fact of what Detule and arrrghhh were talking about with JB's new audio routing that was put in place in the libhtc_acoustic.so file. I opened it up in Notepad++... I found that the file was referenceing the .CSV files from WM and not the ones originally in FRX07 /system/etc. So for instance instead of looking for AudioPara4.csv (FRX07 orginal file) it was looking for AudioPara3.csv. Plus it was looking for the AudioPreProcessTable.csv and the AudioFilterTable.csv.
Now when ever I've tried to add JB's libhtc_acoustic.so to my system/etc folder and boot all things would work until any audio was played it would reboot my phone, so I'm sure there are other items which need to be corrected... I used to do some C programming about 20 years ago... Along with several other programming languages... I've looked for the source/changes JB made but couldn't seem to find it on gitorious...
If someone could point me to it I would be interested in parsing through to see if I can pick up anything of interest.
Thanks for everyones feedback so far... If anyone else has had success or failures I would like to know what has worked and what hasn't...
Hey.
Been working with XDAndroid on my TP2 for a while. Loving it.
Got a RHOD400, FRX07, Sprint model. Worldphone.
Bluetooth works natively on WM.
It turns on and my computer pairs with my TP.
However, it never connects.
I tried connecting it to my tablet, and nada. It just pairs, but never connects. So...I don't know what I'm missing or doing wrong. I've tried waiting, but twenty minutes pass and nothing.
Any ideas? Experiences? Or does BT not work with FRX07.1. On the thread it said it does, so wondering if it's an end user issue.
Thanks.
It *kinda* works. I don't think it's been seriously tested/investigated. AFAIK some developers did get it to transfer data, and I know several users have gotten headsets/car integrations to work. But I've also heard of other users having issues with no audio passing on the headset for example. So it seems hit-or-miss at best. It was only recently enabled, and the developer that was working on it hasn't been around much since it was initially enabled... so no clean-up/refinement has been done (as of yet) on bluetooth...
emwe seems to be enabling it on his .35 tree, hopefully it will work better there.
Thanks very much for the information, makes sense that the development would be a bit behind given it's fairly new release. Didn't think about it that way.
I'm going to keep searching and tinkering, but it's good to know that it's not just my phone going ape****. Thanks.
Hey guys!
I installed Cyanogenmod just a few days ago for the first time.
I was (and still am) very happy with the replacement, but I ran into one issue related to sound. Before I installed cyanogen (on the default ROM) I had an issue with the Skype app: my voice sounded like a chipmunk. I thought it was a Skype problem. After installing this problem was FIXED! I was really happy. But then somebody called me on the ordinary phone and THEIR voice was distorted terribly and I was unable to hold conversation. I googled feverishly and found an "audio policy.zip" in a forum post related to a similar problem. It said I was to flash that file. And I did. Voila, the issue was indeed fixed! BUT, now Skype doesn't get audio input from me at all, and Viber also has a similar problem. So essentially I fixed one problem but got another instead. My guess is that the audio policy file wasn't perfectly configured for my specific phone, and...
that's what I need help with. Either to get a pre-configured file for my specific phone, or for somebody to help me configure it manually. This is what my current file looks like: pastebin.com*ZaTXd1UZ (replace * with / ). Please help.