[LG Optimus 2x] tonyp:
The bluetooth situation

Okay, let me do one last post about bluetooth before it gets totally out of hand.

Google replaced the bluez bluetooth stack with bluedroid in Android 4.2.

Thus arcee (our former device maintainer) had to enable bluedroid in CM10.1.

Unfortunately it doesn't work that well on our phone - I spent two weeks trying to debug it but didn't get any real clues - I'm assuming it's due to some incompatible blobs by LG/Nvidia.

There are mainly two issues: a) bluetooth media "speeds-up" when listening - it hits some right away and others (like me) after 30+ minutes.

What I recently learned is b) bluetooth calling seems broken. I was under the assumption that arcee got it working with bluedroid, but apparently he didn't (could someone confirm that it's broken in the CM10.1 nightlies as well?).

I will update the OP of my threads with this information.

What I did at my CM10.1 ROM: under a giant effort I replaced the bludroid stack with bluez again.

I combined the work of android-bluez and CodeAurora. The latter has the (way) better and (way) less hackier implementation, but unfortunately it only works with qualcomm devices, so I had to use some of the hacks from the former to bring it up.

Due to the hacks the Phone app doesn't work anymore with bluetooth. Thanks to the work at andorid-bluez I can forwardport the bluetooth stuff from the CM10 phone app (this is what I did in my CM10.1 t-builds ROM) - then bluetooth calling works again.

But unfortunately the code is outdated and the hacks break the Phone app when compiled with a GCC 4.7 or GCC 4.8 toolchain. I were not able to fix that - that's the reason bluetooth calling doesn't work in my CM10.1 TheROM build.

To sum it up: Apparently the only way to have bluetooth calling working in a ROM (>CM10) is by using bluez plus the Phone app hack/forwardport and compile it with GCC 4.6.

When you rely on it you can use my CM10.1 t-builds (or a ICS / CM10 ROM!).

My TheROM is built for me and thus was compiled with a newer toolchain which breaks BT calling.

Personally I don't need bluetooth calling and prefer the speed of the newer toolchain - and I do not have the time anymore to maintain the same ROM build with different toolchains.

Google updated the toolchain to 4.7 by default with Android 4.3, thus I am certainly not going to try and hack the phone app again and use the old toolchain just to get it working.

This requires way too much work for CM10.2.

Soo.. I think I am aware of the situation, or did I miss something? If you don't have anything useful to add please restrain from further posting about bluetooth - it is just annoying and doesn't help at all.

I certainly don't need reminders that it's broken - I do KNOW that! If I could fix it I would, but I did not manage to.

When and if I find the time I will try to include bluez into CM10.2. I had prepared for the Android 4.3 drop and cleaned up my source code (separated the bluez code form bluedroid), but it will still take lots of time to include, port and debug it properly.

I do NOT know when I will find the time. Do it yourself if you need it now, but stop complaining (and yes, I count each post abour bluetooth being broken as complaining!).

Really - what are you trying to achive by constantly posting about it? If you're a dev who can provide something useful: for sure go ahead!

But unfortunately ALL posts I read about it are just mentioning that it's broken - WHICH I AM AWARE ALREADY for gods sake!

As I don't really need bluetooth all you are doing is driving me away from doing anything else for bluetooth, ever. I would do it for YOU guys, for those who need it, not for myself

But by constantly ignoring my requests to leave it you're really starting to annoy me. So why should I take my personal, limited, free time to help you, if you keep ignoring me?

Are we clear?

Please note that this post is not directed at someone specifically, just a general explanation (and rant) about the situation.

Yes, I think the comment was needed. While I appreciate your donations I posted several times that I don't appreciate questions about bluetooth.

Yes, it is certainly possible, as pretty much everything is possible with Android - but it's not within my time limits and/or abilities.