Related
Hi guys,
i recently received my iTech R35 A2DP Bluetooth Headset for my Touch HD which is identical to HTC BH S100 since its only rebranded.
Pairing, controls and everything works fine, but when playing music the connection constantly gets lost for short terms regardless of the distance between the phone and the Headset.
The weird thing about it is, that the headset works perfectly with my friends HD. He even could go away like 10m without any kind of interruption.
I already tried some different settings with HD Tweak but no improvement.
Besides I noticed that overall bluetooth performance with my phone, as it once took about 30 minutes to send a 50MB file, isn't that good.
Thanks for any help!
Update:
I tested the Headset today with two other phones (SE W950i and some Nokia). It worked perfectly so I figure something has to be wrong with my phone. I'll perform a hard reset on the weekend and see if it changes anything. Otherwise I'll have to contact the customer service.
Has anybody here experience with german support. If I had to send the phone in, how does it usually take til u get your phone back?
Well, I just performed the hard reset and it solved the issue. Very strange since I hadn't installed that much programs.
Well, the problem returned and I now figured it out in detail.
There's no correlation with the programs installed.
Once the Bluetooth headset is in the Bluetooth-Device-List as it was connected before the constant lags are there.
If I delete it and re-pair the headset the lags are gone for this one time until the headset got disconnected. Even if I get out of range and return in reach connection is crappy from then on.
Didn't anybody recognize such a strange behaviour too?
I have a similar issue with my Sony Ericsson HBH-IS800 phones.
I thought I'd solved it by re-pairing with the handset, and initially that pairing seemed to last for a while, but now it seems I have to re-pair at least once a day to avoid the stuttering (it's really bad, isn't it?)
Frankly, I'm getting pretty disenchanted with my HD. Every time I discover a tweak which sorts an issue, another issue raises its head. I've lost count of the many hours I've spent trrying to get it to work as it ought to.
Wishing I'd got an iPhone. Okay it's not as good on paper, but at least everything works....
I have to agree the bluetooth is dodgy for me at the best of times in trying to connect to any computer.
Surprisingly, Ive had a good file transfer between my HD and MaxOSX, I can't say the same for Windows XP or Vista where on both accounts it has failed to connect via bluetooth to perform an active sync.
Petee said:
I have a similar issue with my Sony Ericsson HBH-IS800 phones.
I thought I'd solved it by re-pairing with the handset, and initially that pairing seemed to last for a while, but now it seems I have to re-pair at least once a day to avoid the stuttering (it's really bad, isn't it?)
Frankly, I'm getting pretty disenchanted with my HD. Every time I discover a tweak which sorts an issue, another issue raises its head. I've lost count of the many hours I've spent trrying to get it to work as it ought to.
Wishing I'd got an iPhone. Okay it's not as good on paper, but at least everything works....
Click to expand...
Click to collapse
Thanks for your information. At least I'm not the only one with this issue.
Meanwhile I tested this behaviour with my buddies HD and it's the same pattern with his one.
I contacted german support today and will report after their answer.
i've been having the exact same problems with my hd. i would be able to pair it with my landrover, but then the connection would be lost. (there's another thread on this somewhere).
anyway, i tried installing BTRestore and BTRestart along with Mortscript and a custom script to help keep the bluetooth active. however, my problem was not that the bluetooth was turning off, but that the connection would not stay active.
so i installed a custom rom, Dutty's version 1.7, and also installed jetware bluetooth program (www.jetwaremobile.com); so far so good (*fingers crossed*). this is my 3rd day and the bluetooth works great. the phone connects with the car instantly, my phonebook works and i can make and receive calls without losing the connection.
so maybe updating the rom will help you too.
Sorry, it's been a while since HTC answered my questions but since their answer was quite disappointing I had no rush to post it.
Summarized they told me the HTC BH S100 was not compatible with the Touch HD even though I pointed out that it's in compatibility-list of the Diamond and both are running the same Chipset and OS and that it works fine after the first pairing.
As I'm tired of reconfiguring my phone I'll wait some time to flash another ROM. I hope WM 6.5 will be released soon and fix this problem, too.
Hi there, my first post on a bug I think I've found in Sentinels ROM v4.80 for my Nexus 10 32GB.
Problems arises when trying to sync up Sixaxis utility to PS3 controller - it worked fine in the previous version now not working at all. Have tried various permutations of ROM and the default kernel and also tried Trinity Kernel still no bluetooth/sixaxis sync.
I have performed a full wipe as per instructions in SentinelROM thread.
Would be grateful if you could look into this as this is my fave ROM by far :laugh:
Have tried ParanoidAndroid, Cleanrom, Saber, EOS, Purity (comes close but AOSP browser crashes every 2-5 mins).
I would also like to take the opportunity to say thank you to all the developers:good: I've been trying roms since the early days of my HTC G2, through Xperia Play, Nexus 4 and Nexus 10 and it's been a wild journey:fingers-crossed: sometimes:laugh:
All the best
Just updating this thread as other folks are having problems with connecting bluetooth devices using Sentinels ROM v.4.80. Hopefully it'll be fixed in the next version:good: Fantastic job on the ROM otherwise
4.80 blutooth
Tablet talk no longer works with 4.80 over blutooth either.
Have a stock unrooted N4 running the new 4,4,3.
Updated to 4,4,3 solely in the hope it would solve the bluetooth disconnects experienced. Note I did not have 'stuttering' or the like, just solid disconnects which would then auto reconnect in 30-60 sec unfortunately stopping my music app which would then need to be restarted and since I primarily use the BT on my bike or motorcycle it is obviously a pain ....
!!!!!!!!!!!! the update not only has not stopped the disconnects it has now introduced stuttering on occasion (not all the time) ....
Here's where I am at:
1. Live with it until Google finally realizes IT'S A PHONE not a camera or whatever and solves the BT problem or gets the BT folks to do it. (really can't believe they can't solve this or is it just an N4 problem?)
2. Root the phone, install TiBU, backup, wipe and install 4.4.3 factory images, reroot and recover stuff from TiBU ... all this in the hope the BT problem goes away ... chances of this?????
3. Give up and install CM which people say does not have this BT problem ... true??????
Thanks in advance to all for your help and opinions ..........
Could it be
Could it be the BT device itself? Does it work like a charm with other devices?
Electrospaz said:
Could it be the BT device itself? Does it work like a charm with other devices?
Click to expand...
Click to collapse
That's a great question and I am sorry I did not include the info in my original post ... the problem is evident with several different BT devices and these same BT devices work fine connected to other things ..... but not with the N4
zdrifter said:
That's a great question and I am sorry I did not include the info in my original post ... the problem is evident with several different BT devices and these same BT devices work fine connected to other things ..... but not with the N4
Click to expand...
Click to collapse
Has it always been stock? Perhaps your BT adapter in the device is faulty itself. I've ran two different headsets off of mine in the past year as well as connected to my PC and other phones with no issues at all. I've been rooted running beanstock right from day 1 though..
Electrospaz said:
Has it always been stock? Perhaps your BT adapter in the device is faulty itself. I've ran two different headsets off of mine in the past year as well as connected to my PC and other phones with no issues at all. I've been rooted running beanstock right from day 1 though..
Click to expand...
Click to collapse
Yup ... always stock ... when new on whatever version was current then (can't remember) did not have this problem and BT worked fine ........ when they went to the 'low power' BT solution it started.
Was really hoping this update would solve the disconnect problem.
I've read around, and multiple people are having this issue, without any real solution. Does anyone know of a rom with which bluetooth is stable (or do I have a hardware issue?)
When Bluetooth is connected to any handsfree car system , it cuts out for a few seconds before reconnecting. For example, If I am in a call, it will revert to the built in earpiece & disconnect from the car , only to reconnect seconds later. Same of Bluetooth audio (a2dp). It's fairly disjointed.
I've tried both stock android 4.4.4 & the lastest Cyanogenmod snapshot & nightlies.
Thanks for any help, and I will post back if I find anything useful.
Never happened to me, I've connected with jawbone FM music transmitter, and with several other Bluetooth peripherals including headphones, my smartwatch, and a mono headset and not experienced this. Maybe its a problem with the specific car your trying to connect to? My BMW 750li doesn't pair with the nexus 4, and even a bb z10
Edit: if multiple people are reporting this and multiple hands free car systems don't work then maybe is a hardware issue? Which revision nexus you have ?
Blazing angel said:
I've read around, and multiple people are having this issue, without any real solution. Does anyone know of a rom with which bluetooth is stable (or do I have a hardware issue?)
When Bluetooth is connected to any handsfree car system , it cuts out for a few seconds before reconnecting. For example, If I am in a call, it will revert to the built in earpiece & disconnect from the car , only to reconnect seconds later. Same of Bluetooth audio (a2dp). It's fairly disjointed.
I've tried both stock android 4.4.4 & the lastest Cyanogenmod snapshot & nightlies.
Thanks for any help, and I will post back if I find anything useful.
Click to expand...
Click to collapse
I suspect people are experiencing different issues, since no 2 cases appear to be the same. As for me, I have a 2008 Audi with integrated BT which worked fine with Gingerbread. 4.+ has been very different: the connection would often be lost and regained mid-trip and worst of all, 9 times out of 10 I couldn't initiate or terminate calls from the car. That last point is a deal-breaker for me...
Some early KK builds were fine, in fact I used Purity till March. Then a new build came along which returned the above issues. Since then I have tried virtually all the popular ROMs (I would create a Nandroid backup and reflash after a day or so - I still try new builds), and at least for me the AOSP ROMs all have the same issue, above.
I am currently using AICP ROM which is AOKP, nightlies are installed OTA and I don't have a single issue with the car BT any more. And it's a very stable ROM, I´ve been using the ROM for about 4 months I think.
Your mileage may vary, since I suspect we all have different issues, but the AOKP branch works for me. Dirty Unicorns works fo rme too.
BassBlaster said:
Never happened to me, I've connected with jawbone FM music transmitter, and with several other Bluetooth peripherals including headphones, my smartwatch, and a mono headset and not experienced this. Maybe its a problem with the specific car your trying to connect to? My BMW 750li doesn't pair with the nexus 4, and even a bb z10
Edit: if multiple people are reporting this and multiple hands free car systems don't work then maybe is a hardware issue? Which revision nexus you have ?
Click to expand...
Click to collapse
It is a rev_11
paul c said:
I suspect people are experiencing different issues, since no 2 cases appear to be the same. As for me, I have a 2008 Audi with integrated BT which worked fine with Gingerbread. 4.+ has been very different: the connection would often be lost and regained mid-trip and worst of all, 9 times out of 10 I couldn't initiate or terminate calls from the car. That last point is a deal-breaker for me...
Some early KK builds were fine, in fact I used Purity till March. Then a new build came along which returned the above issues. Since then I have tried virtually all the popular ROMs (I would create a Nandroid backup and reflash after a day or so - I still try new builds), and at least for me the AOSP ROMs all have the same issue, above.
I am currently using AICP ROM which is AOKP, nightlies are installed OTA and I don't have a single issue with the car BT any more. And it's a very stable ROM, I´ve been using the ROM for about 4 months I think.
Your mileage may vary, since I suspect we all have different issues, but the AOKP branch works for me. Dirty Unicorns works fo rme too.
Click to expand...
Click to collapse
Thanks for the responses. The cars work perfectly fine with galaxy phones & iphones, the issues lies with my nexus sadly. I will try the posted roms later on and update!
Also Paul, can you post a link to the rom you have installed? I've been out of the loop for a while and cannot find it !
Mine is also a rev11, 303k. I guess that rules out hardware issue
Blazing angel said:
It is a rev_11
Thanks for the responses. The cars work perfectly fine with galaxy phones & iphones, the issues lies with my nexus sadly. I will try the posted roms later on and update!
Also Paul, can you post a link to the rom you have installed? I've been out of the loop for a while and cannot find it !
Click to expand...
Click to collapse
Here you go: http://forum.xda-developers.com/nexus-4/orig-development/rom-aicp-3-5-kk-4-4-2r2-mako-t2632777 - enjoy!
This is the official download page, where you can get the gapps package you prefer, plus the release/latest nightly.
If you install the release you won't get the nightly updates. The nightlies are very stable, so I'd recommend the latest nightly.
I'm experiencing exactly the same problems than Blazing angel.
Bluetooth is unusable in my car, "Unfortunately, the process com.android.bluetooth has stopped" being displayed repetitively.
I suspect it's not hardware related as I do not have problem using the stock or paranoid ROMs. Unfortunately, my favorite ROMs (AOKP, CN or Carbon) are causing problems.
Do you think it's possible to pickeup some files in the paranoid files and inject them to Carbon to solve the problem ?
Thanks in advance for your help !
paul c said:
Here you go: http://forum.xda-developers.com/nexus-4/orig-development/rom-aicp-3-5-kk-4-4-2r2-mako-t2632777 - enjoy!
This is the official download page, where you can get the gapps package you prefer, plus the release/latest nightly.
If you install the release you won't get the nightly updates. The nightlies are very stable, so I'd recommend the latest nightly.
Click to expand...
Click to collapse
Great ! I was able to bypass my bluetooth problem using this Android 4.4.4 rom, without loosing great features of Carbon or Pac-ROM ! :victory:
Thanks for sharing this ROM Paul ! :good:
I *REALLY* don't want to buy a different phone, but.... I recently swapped out the headunit in my truck from a Clarion to a Kenwood due to phone audio problems with the Clarion. So now the phone over BT with the Kenwood works great but the audio over BT is skipping and breaking up. Seen lots of posts about this being a problem, but no solutions. Sometimes rebooting the phone helps, but not usually. Sometimes forcing Bluetooth Share to close will help, but not usually. I've deleted and re-paired the devices.
I am currently running the stock 6.0 ROM, build 24.49-18, only rooted. The phone says it's up to date.
On to my point... do any of the alternate ROM's seem to have the BT audio issues worked out??
djmasters said:
I *REALLY* don't want to buy a different phone, but.... I recently swapped out the headunit in my truck from a Clarion to a Kenwood due to phone audio problems with the Clarion. So now the phone over BT with the Kenwood works great but the audio over BT is skipping and breaking up. Seen lots of posts about this being a problem, but no solutions. Sometimes rebooting the phone helps, but not usually. Sometimes forcing Bluetooth Share to close will help, but not usually. I've deleted and re-paired the devices.
I am currently running the stock 6.0 ROM, build 24.49-18, only rooted. The phone says it's up to date.
On to my point... do any of the alternate ROM's seem to have the BT audio issues worked out??
Click to expand...
Click to collapse
Answering my own question.....
I ended up trying another ROM, AICP for clark, and so far AVRCP is working fine, it has connected/disconnected several times and has always come back quickly and without any skipping/stuttering. I haven't tried the phone over BT yet. And it's a pretty good ROM beyond that!!!
djmasters said:
Answering my own question.....
I ended up trying another ROM, AICP for clark, and so far AVRCP is working fine, it has connected/disconnected several times and has always come back quickly and without any skipping/stuttering. I haven't tried the phone over BT yet. And it's a pretty good ROM beyond that!!!
Click to expand...
Click to collapse
I was wrong, after a couple of days AICP started doing the same thing. Replaced XT1575 with an HTC 10, I wish the screen was larger but it's a really nice phone!!! And no Bluetooth troubles.
My phone is connected to my car radio any time I'm in the car, and not having this issue. I'm still on 5.1.1 stock but rooted. Headunit is a Alpine CDE-W235BT. I've had it hooked up 5+ hours at a time. No issues with media or phone calls.
Yeah, it works for some but not for others... I think it's more headunit dependent... my Clarion was OK for music but the phone was jacked up. Reverse with my Kenwood, phone OK but audio jacked. Either way, it had to go.....
Factory rom is the only one I can get to work properly with BT in my Mercedes
I haven't tried it on the Moto X Pure, but on the 2nd gen Moto X, Cyanogenmod had infinitely better bluetooth strength than the stock rom, or any other rom I tried. I'm not saying it's the same for the Pure, because they're probably maintained by different people, but worth looking into at least.
Bluetooth usually connects between my Moto X Pure and Mazda3, but there is a 35% chance that when I turn on my car the audio will connect in this really strange manner where tracks skip and the audio sounds horrific. The only solution is to disconnect and reconnect again, which takes another 30 seconds.
Every ROM I have tried on Moto X Pure has had this problem:
Stock, CM13, AICP
It's gotten so annoying that I've decided I am going to sell my Moto X Pure and revert to my Galaxy S4. Never have ANY problems with my old Galaxy.