Hi i have a problem when using the mytouch slide (rooted) with bluetooth devices. Im currently running Cyanogen nightly build 141 with a Motorola S7- hd bluetooth headset. the media Audio works fine as i can use the controls with the music app. but when switching to make a call i cant hear anything. any way to fix this issue thanks
This is a known problem with froyo builds on the Slide. I think it's partly due to the fact that HTC haven't released the source code for the bluetooth stack yet.
The simple fix is to use a 2.1 ROM, or wait for T-Mobile to deign to release a 2.2 ROM for the Slide so that the devs can incorporate the fixes into their own ROMs.
I have tried many cooked ROMS, Darkys, DOC for example and several others. They are all great and fast, a few bugs here and there, but in general I'm a fan, but.
Everyone of them breaks the bluetooth rSAP profile and makes my phone pretty unusable in my Audi.
Symptoms are dropping connection, no phonebook (or intermittent) transfer. No connection at all after it drops until phone is rebooted. Similar problems are with HFP bluetooth profile as well. This is with any cooked ROM.
My only solution to the issues was to install a stock gingerbread 2.3 JVK ROM with no mods.
I have posted a few times on the developers threads but nobody seems interested.
So just a message to developers, what could it possibly be that you are all doing that breaks the bluetooth so badly?
Maybe try a cooked rom but using stock kernel. Don't even root it. If it doesn't than probably it has something to do with the kernel.
Possibly, but most cooked ROMs come pre-rooted with tweaked kernels.
I guess I could build one in the DOC's kitchen without any tweaks.
You only talking about 2.3.3 ROMS? Or does Darky's V9.5 do it as well? If 2.2.1 works fine on a custom ROM, that would be more important to me than having a non-stable gingerbread ROM until Samsung release an official update? V9.5 is pretty unreal so I see no reason to bother with 2.3.3 yet That is if you rely on bluetooth working in your car more than 2.3.3 ^_^
craigyb said:
I have tried many cooked ROMS, Darkys, DOC for example and several others. They are all great and fast, a few bugs here and there, but in general I'm a fan, but.
Everyone of them breaks the bluetooth rSAP profile and makes my phone pretty unusable in my Audi.
Symptoms are dropping connection, no phonebook (or intermittent) transfer. No connection at all after it drops until phone is rebooted. Similar problems are with HFP bluetooth profile as well. This is with any cooked ROM.
My only solution to the issues was to install a stock gingerbread 2.3 JVK ROM with no mods.
I have posted a few times on the developers threads but nobody seems interested.
So just a message to developers, what could it possibly be that you are all doing that breaks the bluetooth so badly?
Click to expand...
Click to collapse
I had same problem... I've changed the kernel to Supercurio kernel and since then not even single problem, else I use to have same problems as u having and were happening several times in a day. Cook a rom in romkitchen with SC kernel and see if that help
It has happened since around 8.0 of Darkys ROM, I must admit I have always used Voodoo Kernels with lagfix, so maybe an SC kernel will fix the issues.
I just installed the stock gingerbread 2.3.3 yesterday afternoon and I've had no issues since, before that the highest release I used was JS8 with the latest ginger modem JVK?
I was on 2.2.1 Ultimate and there wasnt any issues with BT headset stereo using headphone and media profile. It was also working fine with my MB car connections.
Now I'm on Criskelo GB and besides the crappy sound of gingerbread, bt still not an issues with MB car or headset. Criskelo is based on DaminGTO kernel.
It was also working on the Pioneer BT Audio receiver, xplod series.
I never had those problems with using Stock FW.
Now iam on JVK erveryting is fine.
Iam on rSAP with a Mercedes Comand NTG1 + V2 BT Module.
One thing never worked, is the PBAP Phonebook Access Profile,
so only the sim contacts are visible in the comand!
Ok, stock JVK is ok and a cooked JVK ROM from the kitchen with a supercurio kernel is ok as well.
Full phonebook/dialled/missed/received transfer in rSAP mode to my Audi A7 with MMI 4G.
So it seems the issue is Voodoo kernels.
Since 4.22, any high frequency audio streamed across bluetooth A2DP is terrible. Sounds like it's being clipped....static and popping (see code issue here, https://code.google.com/p/android/issues/detail?id=39632).
Well, it hasn't been fixed in v4.3. However, someone edited the stock bluetooth.default.so file and created a fix. I've been using it before 6+ months. It's been working great.
Wondering if there's someone who has the skills and is willing to to the same. Here's the post where it was fixed for 4.22 (https://code.google.com/p/android/issues/detail?id=39632#c158)
Hello, I'm running the latest GoldenEye ROM that's over in the AD forum. There is a call recording mod that you can flash to enable call recording. It works absolutely wonderful!...as long it's with the handset itself. I've been trying to figure out a way to enable it over bluetooth. With many many failed attempts, I'm now looking for something third party that I can use that will work with GoldenEye and enable recording over bluetooth.
GoldenEye is pretty much a stock ROM with some minor tweaks here and there and runs the adam kernel. If anybody has figured this out, or has a workaround to get it to work please let me know! Thank you very much.
Just wanna bump this up to see if anybody has heard anything new
Hi,
I have a very annoying problem with my Note 3.
Currently I am on Temasek V50.1 and before that I was on official 4.4.2.
My problem is that I can't really watch YouTube videos with the official app because the quality is just atrocious (on CM and official KK).
I tried reinstalling it and cleared cache. Nothing worked.
Next I installed this: http://forum.xda-developers.com/showthread.php?t=1529715
([MOD] YouTube 4.4.11 (v5b), *1080p* / 720p HD (over WiFi & 3G), screen off playback)
The quality of the videos definitely improved but I still get this message: http://imgur.com/hiwjOYc
Plus it is a older version and I would like to use the newest of course.
Does anyone else have the same problem? Is there anything I can do about it?
Thanks in advance!