Bluetooth and Android?

[arrrghhh]

Originally Posted by Tippfehler

I think, it is not impossible, because LV is running on all other android phones, f. i. HTC HD2 (Leo). There is only a bad program (liveview app) that is crashing the bluetooth stack.

I'd say you'll need to sort out the 'why'. Logs are going to be required.

[Tippfehler]

I have already uploaded logs (0 views).
You can find it in the linked posts:
the newest with FRX07:
http://forum.ppcgeeks.com/2130115-post98.html
Please excuse the links to xda-developers.
older logs with FRX06:
xda-developers - View Single Post - [TESTING] New audio routing for Froyo
here for Rhodium, Diamond and Wildfire (to compare ... LV ist running nearly perfect on wildfire):
xda-developers - View Single Post - Sony Ericsson LiveView™ Issues

[arrrghhh]

Originally Posted by Tippfehler

I have already uploaded logs (0 views).
You can find it in the linked posts:
the newest with FRX07:
http://forum.ppcgeeks.com/2130115-post98.html
Please excuse the links to xda-developers.
older logs with FRX06:
xda-developers - View Single Post - [TESTING] New audio routing for Froyo
here for Rhodium, Diamond and Wildfire (to compare ... LV ist running nearly perfect on wildfire):
xda-developers - View Single Post - Sony Ericsson LiveView™ Issues

Didn't realize you took so many logs - there's no bug for this on the bugtracker...

Edit - a lot of the logs also appear to be from FRX06... which you manually enabled BT on I assume?

Edit 2 - Hrm. Definitely see some serious failures there. Open a bug on the tracker, assign it to jb if you can... not sure if you'll be able to assign it to him or not, but he needs to look at this for sure.

[Tippfehler]

Yes, I have the most logs from FRX06 with the manual BT-changes for rhod (for BT on Diam100 is no change required) and one from FRX07. I think, there is no difference.
I have no idea, how I can add something to the bugtracker. If I find enough time tomorrow, I will take a look at the bug-tracker.
Thanks.

---Edit---
I have tried, to add it to the bugtracker and hope it is in the right section.
http://bugs.xdandroid.com/show_bug.cgi?id=143
It was not possible, to assign it to jb, because I do not know his address. (jb@xdandroid.com is unknown)

[arrrghhh]

Originally Posted by Tippfehler

Yes, I have the most logs from FRX06 with the manual BT-changes for rhod (for BT on Diam100 is no change required) and one from FRX07. I think, there is no difference.
I have no idea, how I can add something to the bugtracker. If I find enough time tomorrow, I will take a look at the bug-tracker.
Thanks.

---Edit---
I have tried, to add it to the bugtracker and hope it is in the right section.
Bug 143 – Sony Ericsson Liveview Application 1.0.A.0.18 is crashing bluetooth
It was not possible, to assign it to jb, because I do not know his address. (jb@xdandroid.com is unknown)

Yea, I saw the bug on the tracker. I don't think jb has a XDAndroid email... I'll see if I can assign it to him, thanks. I just want him to be aware of the issue...

[mgross029]

Not sure if anyone is still looking at this thread but I put some of my findings for in-call routing for BT together over at XDA...

Good Luck! Hope it works for others...

[machek]

Originally Posted by mgross029

Not sure if anyone is still looking at this thread but I put some of my findings for in-call routing for BT together over at XDA...

Good Luck! Hope it works for others...

I'll try it today. What headset are you using? I'm using a Motorola Roadster and I'll give it a try in a couple of hours and report my findings

[mgross029]

Originally Posted by machek

I'll try it today. What headset are you using? I'm using a Motorola Roadster and I'll give it a try in a couple of hours and report my findings

I am using the Motorola H710, but I've done it with my cars BT connection too... Just a little more cumbersome to do so I've stayed with the Headset...

[machek]

I couldnt get it to work on mine. It seems like my bluetooth has trouble staying paired.

[Technix2002]

I can say that FRX7.1 right out of the box works with A2DP and regular BT Headset, but the couple really odd things are:
Jawbone has to be re-paired every time I boot back into Android (no bigge really)
Jawbone once paired doesn't initially route call audio (while in call with BT selected as output, if I dis/re-connect headset call audio will route only while in the that call, each new call has to go through the same steps)

Anyone have any ideas as to why this is or how to fix it (I'll gladly take the latter over the former, ha!)

Once again, not complaining. This has become quite incredile that my TP2 is running Android well enough to use it quite regularly!