Hi!
Be gentle =O) my first post here!
I got some problems using inbuild car handsfree connected via Bluetooth.
It worked great with stock rom, but with omnirom there's unrecognizable robotic voich and "audio scratches"
Phone and car pairs without any problems and "speaks" with each other with info, cals etc, but the audio is horrible (Roboic noises).
I like Omnirom very much, but for me it is very importent that the connection between car and phone is flawless...
SGS3 I9300 and always the latest Omnirom Nightlies
Magnum81 said:
Hi!
Be gentle =O) my first post here!
I got some problems using inbuild car handsfree connected via Bluetooth.
It worked great with stock rom, but with omnirom there's unrecognizable robotic voich and "audio scratches"
Phone and car pairs without any problems and "speaks" with each other with info, cals etc, but the audio is horrible (Roboic noises).
I like Omnirom very much, but for me it is very importent that the connection between car and phone is flawless...
SGS3 I9300 and always the latest Omnirom Nightlies
Click to expand...
Click to collapse
Unfortunately your device is not maintained any more. (It's one of many devices we're dropping with L, and I'm going to tlak with the team about stopping nightlies for long-unmaintained devices soon.)
Related
I was just wondering if anyone else was having problems with a bluetooth headset using Cyanogenmod 10.1? The call quality while using the handset is great, but when I use my bluetooth (Jawbone Era, Motorola Sliver Elite) the call quality is absolutely terrible, the person can't even hear what I'm saying.
I say Cyanogenmod because that's my favorite rom, but it also happens on AOKP, PAC, ParanoidAndroid, and pretty much every other Vanilla type Rom.
Any help or suggestions?
The same problem with Jawbone Era. All works fine in Samsung stock 4.1.2 ROM.
Yep. I have this problem, too.
Bummer, as I'm writing a Bluetooth headphone round-up for a magazine this month, and I can't review call quality without borrowing a friend's phone.
Known Issue
Hey guys the bluetooth isssue your speaking of is a VERY well known issue in CM its one of the few bugs that is still being ironed out. Its also present in basically every other aosp type rom because they are all based on CM. The awesome cyanogen devs are working on it constantly and im sure they will get it figured out :good:
So if you here any reference of an "upstream" issue in a ROM thread its most likely referring to it being an issue in CM and therefore the ROM in question. :good:
Bluetooth car connections drops and really bad audio quality when on call.
FanDroid09 said:
Hey guys the bluetooth isssue your speaking of is a VERY well known issue in CM its one of the few bugs that is still being ironed out. Its also present in basically every other aosp type rom because they are all based on CM. The awesome cyanogen devs are working on it constantly and im sure they will get it figured out :good:
So if you here any reference of an "upstream" issue in a ROM thread its most likely referring to it being an issue in CM and therefore the ROM in question. :good:
Click to expand...
Click to collapse
Hi everyone, I have used PARANOIDANDROID in the past for Samsung Note and had a great experience using it. Just installed the PARANOIDANDROID on my new HTC one.
I am having two issues that are forcing me to go back to a stock rom,.
1st) Bluetooth connection with car, when calling the audio quality is really bad. The person on the other end cannot understand what I am saying.
2nd) when on a call with a headphone /w mic and connected to my Mac, the mass storage keeps going on and off. This affects the audio quality of the phone call.
All other issues that have been reported here I am OK to way for, but the BlueTooth issue forced me to look for a stock ROM for now.
I hope the great the people working on these Rom ( Paranoidandroid and Cyanogenmod ) can fix these issues quickly.
no bluetooth for voip apps
I've tested CM on note I and II, the same issue shows up, I cannot use bluetooth with voip apps. Same goes for 10.2. Too bad
I'm using CarbonRom is both HD and HD+ and this problem is the same for both. Today, I made a phone call and the person wasn't getting enough volume and the words were garbled. I tried the headset with Google Voice search and VoiceToText in other apps. It is evident that the mic isn't working correctly. I tried a different wired headset and the result was the same. For reference the headsets are a Klipsh S4A and stock that comes with Galaxy S3. The onboard mic works as expected. I paired a Bluetooth headset and, surprisingly, that worked the best of all.
Sometimes this is a kernel issue. I reflashed the rom without the fstrim kernel and that made no difference.
I am thinking that this is a bug that may be in the various Android, custom roms and that's why I didn't post only in CarbonRom thread. It may even be a problem with stock. I don't think there are many people that use a wired headset with mic. I make phone calls with MagicJack.
Maybe a few people that have a headset with mic can try and report back if this is a problem for the particular rom they are using.
someone here http://forum.xda-developers.com/showthread.php?t=2388088 mentioned it worked with cm 10.1, maybe that one would work for you
king200 said:
I'm using CarbonRom is both HD and HD+ and this problem is the same for both. Today, I made a phone call and the person wasn't getting enough volume and the words were garbled. I tried the headset with Google Voice search and VoiceToText in other apps. It is evident that the mic isn't working correctly. I tried a different wired headset and the result was the same. For reference the headsets are a Klipsh S4A and stock that comes with Galaxy S3. The onboard mic works as expected. I paired a Bluetooth headset and, surprisingly, that worked the best of all.
Sometimes this is a kernel issue. I reflashed the rom without the fstrim kernel and that made no difference.
I am thinking that this is a bug that may be in the various Android, custom roms and that's why I didn't post only in CarbonRom thread. It may even be a problem with stock. I don't think there are many people that use a wired headset with mic. I make phone calls with MagicJack.
Maybe a few people that have a headset with mic can try and report back if this is a problem for the particular rom they are using.
Click to expand...
Click to collapse
Yes, I can confirm this issue, apparently.
I'll try to see what could be done.
Does the 12-12-13 update include kernel changes which are suppose to repair black box issue in default browser api ?
UPDATE: Forgive my ignorance. I now see the commits included in Milaq's CM11 KK 4.4.2 update for the TouchPad (tenderloin). And understand the devs are still working updating 3.6 kernel. So will need to live with the Kernel 2.6.35 for a while longer. But until then apps utilizing default browser api are problematic. At least Chrome and Firefox are working.
I'm running Milaq's 4.4 ROM also. Happy to run with it for now even with "black box" issues, is running incredible smooth so far. Using shortcuts to Chrome bookmarks is my workaround for Gmail etc just now, although same issue in the BBC news app (and others I'm sure
I don't have enough posts to post or reply in development forum so posting here.
On the CM11 dev thread a couple posts about audio issues. I've flashed the 12/10, 12/12 & 12/14 CM11 nightlies and have not observed/heard audio issues.
And BT and WiFi are working ok. And file transfer via USB and BT ok (although BT transfer appears slower from what I recall in CM7/CM9 or WebOS).
Haven't yet figured out how to get BT streaming (from a Windows PC) to work.
If I could get my Plantronics Backbeat 9033+ BT headset to charge correctly, I could test those with CM11 (previously I the BT headset working well in CM9 as well as WebOS). Wish I never bought this particular headset, as they hurt my ears, no matter which eartips I use. And now will not charge. (I only used a few times since purchasing late last spring). Need to look up my warranty. Sorry I digress OT.
woodytrain said:
And BT and WiFi are working ok. And file transfer via USB and BT ok (although BT transfer appears slower from what I recall in CM7/CM9 or WebOS). Haven't yet figured out how to get BT streaming (from a Windows PC) to work.
If I could get my Plantronics Backbeat 903+ BT headset to charge correctly, I could test those with CM11 (previously I the BT headset working well in CM9 as well as WebOS). Wish I never bought this particular headset, as they hurt my ears, no matter which eartips I use. And now will not charge. (I only used a few times since purchasing late last spring). Need to look up my warranty. Sorry I digress OT.
Click to expand...
Click to collapse
When I stated BT was working ok, I was referring to paring the TouchPad with an HP TouchPAd Wireless Keyboard as well with a WIndows XP PC.
I was able to get the BT headset working with my WIndows PC (it was charging ok...issue was operator error). And when I search for BT devices on the TouchPad CM11) my headset displays in the device found list. But when attempting to pair the CM11 Touchpad with the headset, Bluetooth on the TouchPad turns off, and then within a few seconds BT turns back on.
Anyone able to get a BT headset working with CM11...yet?
I probably should just sit back a bit and wait for the updated kernel.
I think i can have my bluetooth headset connected at the same time with my Smartwatch2 but is it possible to have a keyboard and mouse too?
BLiapis said:
I think i can have my bluetooth headset connected at the same time with my Smartwatch2 but is it possible to have a keyboard and mouse too?
Click to expand...
Click to collapse
i have searched & yes,possible...
Bluetooth on the z1 has been totally Crap on anything other than 4.2.2.......
Such a sweeping statement.
I, for one, have had no issues on any firmware with bluetooth
Hi Greg,
Well, when I first got my z1 it was on 4.2.2 and it connected to my car audio system and downloaded the phone book, call logs and I could use the handshake with no problems.. After this (on 290 and 136) it would not work at all. It would pair but I couldn't use handsfree and the call logs and phone book would not download... It got very slightly better on 4.4.2 in that the handsfree and call logs work but not the phonebook... I have tried my car audio with a s3 running 4.3 and a HTC m8 running kitkat and they work with no problems at all.. Handsfree, call lists and phonebook work perfectly... In the Sony website there are hundreds of people that have various issues with bluetooth on the z1....
I have [7.1.2] LineageOS 14.1 [3.4 KERNEL](Invisiblek) on my HP touchpad. For the most part it works great. I have a few touchpads around the house on the wall as my smart home interface. I use the Ring doorbell app and I am able to talk and hear the person at the front door with no issues (connecting via wifi). Apart of that use I want to use it as an intercom (connecting via bluetooth). When I use an intercom app (bluefi), the mic seems to not work. I thought it might be due to the fact the bluetooth is listed as not "working", but I downloaded a voice recorder app and it still doesn't work. If I use 4.4 kitkat, the voice recorder records sound. Any ideas?
Bluetooth doesn't fully work with Lineage14.1
Ntoxic8 said:
I have [7.1.2] LineageOS 14.1 [3.4 KERNEL](Invisiblek) on my HP touchpad. For the most part it works great. I have a few touchpads around the house on the wall as my smart home interface. I use the Ring doorbell app and I am able to talk and hear the person at the front door with no issues (connecting via wifi). Apart of that use I want to use it as an intercom (connecting via bluetooth). When I use an intercom app (bluefi), the mic seems to not work. I thought it might be due to the fact the bluetooth is listed as not "working", but I downloaded a voice recorder app and it still doesn't work. If I use 4.4 kitkat, the voice recorder records sound. Any ideas?
Click to expand...
Click to collapse
The Bluetooth isn't 100% working yet with Lineage14.1. It often sees a connection but either doesn't pair or doesn't work when it does. Evevolv has working Bluetooth, might be worth trying out otherwise stick with the stable and functional Kitkat till the bugs are worked out with newer roms.