Related
I'm curious if anyone else is having this issue or can confirm this is happening on their phone.
I'm pairing my phone up to a bluetooth car stereo (4 different ones) and a couple bluetooth sound docks, and the result is the same no matter what.
If I walk more than a couple feed away the music cuts in and out. it completely disconnects at around 12 feet.
I have never seen bluetooth range this poor, even on my cheepo chinese bluetooth adapter a coulpe years ago.
I called HTC and their only options were telling me to factory reset my phone.
I believe it is by design as part of HTC's "aggressive" power management...I have tried to find a way to increase the Bluetooth power but have not been successful...I have to be no more than 2 feet or so for mine to work..I'm sure there is a way to increase bt power but I'm not sure how...I think I remember seeing this in another thread..
Sent from my HTC One X using xda premium
^It was probably my first thread.
I'm assuming the reason the range is so bad is because the phone is running in low power mode, a feature of bluetooth 4.0.
Yeah, BT 4.0's main attraction is the low power usage. You can't have both great range (the old BT devices) and great battery life. Given a choice, I'd prefer great battery life.
foxbat121 said:
Yeah, BT 4.0's main attraction is the low power usage. You can't have both great range (the old BT devices) and great battery life. Given a choice, I'd prefer great battery life.
Click to expand...
Click to collapse
Bluetooth 4.0 is multiple standards of bluetooth plus a low power version.
It should have better range than bluetooth 2.0, but with the added ability of a low range/low power mode.
The audio will cut in and out even if the phone is just in my pocket and I am using a bluetooth headset (Motorola Elite Sliver). If I cant find a way to fix this or it doesn't work with a different headset I am not gonna be able to keep this phone. I really like the device but the non-existent multitasking and the terrible bluetooth performance is pushing me away. When I work I use my bluetooth all day for either customer calls or just to listen to music/radio on down time and I can't deal with this for too much longer. I'd hate to go back to my iPhone but I may have to unfortunately..
pretty disappointed.
I'm also out of my return policy on this phone now, and they have no other good phones.
Hopefully htc comes out with a fix for this soon.
I've called them 3 times now and havn't gotten a single good answer to why its so bad.
Also emailed them and still no response.
I have also noticed poor range. Much less range when streaming Bluetooth audio to my LG soundbar compared to my iPad and buddies iPhone.
UseYourIllusion said:
The audio will cut in and out even if the phone is just in my pocket and I am using a bluetooth headset (Motorola Elite Sliver). If I cant find a way to fix this or it doesn't work with a different headset I am not gonna be able to keep this phone. I really like the device but the non-existent multitasking and the terrible bluetooth performance is pushing me away. When I work I use my bluetooth all day for either customer calls or just to listen to music/radio on down time and I can't deal with this for too much longer...
Click to expand...
Click to collapse
Same Here.
Me too, This is the worst BT I have ever had on a device.
+1
If my headset is on one ear, but the phone's in the opposite side's pocket. It cuts out.
ackliph said:
+1
If my headset is on one ear, but the phone's in the opposite side's pocket. It cuts out.
Click to expand...
Click to collapse
hey guys, i just bought a One X and im having similar issues. there should be no excuses to have bluetooth cutting out like this on a new phone. My old Desire HD did it and i just thought it was because i had dropped it, but looks like its a HTC thing!
pappas99 said:
hey guys, i just bought a One X and im having similar issues. there should be no excuses to have bluetooth cutting out like this on a new phone. My old Desire HD did it and i just thought it was because i had dropped it, but looks like its a HTC thing!
Click to expand...
Click to collapse
I have no problem at all anywhere in my car, I listen music and radio an average 40 mins a day (while comute). I have a bluelogic bt that came built-in the car.
I also haveno problems and no cutoffs on my stereo bt headphones and I often leave my phone on the table while I workout (true, under 10 feet away). If that matters, I'm on 2.20 stock.
Sent from my HTC One X using xda app-developers app
Same here
i never used bluetooth with my ONE S before now. But I have moved it in to take over my business phone needs and replace my Sensation 4g. It is definately worse range. And if it it 10-15 ft away on the hood of my truck and i turn my headset away from the phone, the signal from my phone can't carry through my head. The sensation had no problems. The newer plantronics headsets are worse than the older ones as well. And putting the phone in my work belt on the opposite side from the earpiece is really bad. I don't know what to do. Might be time to fix my sensation and move back to an old headset.
I was looking online and couldnt seem to find a solid answer regarding Bluetooth 4.0 and what exactly you need to get it to work in the Low Energy way or form. How it works, as in the concept is written in plenty places that explains how it saves power, but there was no clear cut answer as to get that maximum efficiency on battery life.
Basically what i was wondering is, since most new phones have bluetooth 4.0, to get the whole low energy point applicable, does one need to pair it to a bluetooth 4.0 device/headset as well to get that benefit...?? iv been searching online and i can barely find any notable bluetooth 4.0 headsets so was wondering if pairing a bluetooth 4.0 phone (e.g LG Nexus 5), to a Bluetooth 2.1 or bluetooth 3.0 device (e.g Sony SBH52) will still give the same battery saving on the phone with the bluetooth 4.0...??
Or is it necessary for both phone AND device be 4.0 for the BLE to actually work...??
I know the bluetooth will work on these devices, higher or lower number, but im asking specific to the Low Energy usage aspect..
Any insight...?
Sent from my LG-P930 using Tapatalk
Has anyone else for a kernel wake lock of bluesleep quite dominant?
Is there a fix for this?
tangcla said:
Has anyone else for a kernel wake lock of bluesleep quite dominant?
Is there a fix for this?
Click to expand...
Click to collapse
I noticed it today when I had been listening to audio over my bluetooth headphones. Had you been doing similar?
I notice it happens as a result of my Pebble being connected. Do you have any "smart" devices connected to it?
Sent from my D820
Shamingo said:
I notice it happens as a result of my Pebble being connected. Do you have any "smart" devices connected to it?
Sent from my D820
Click to expand...
Click to collapse
Yep I have a Pebble too.
Same here, I have been running it alongside my Nexus 4 (alternating days, same apps, settings, etc.). Nexus 4 is still on Jellybean, Nexus 5 is obviously on KitKat.
The issue might just be with KitKat because I don't have the issue at all with the Nexus 4. My next step will be to flash KitKat on my N4 and see if the issue starts happening there as well.
Obviously there is going to be some sort of battery drain when Bluetooth is enabled but there is a HUGE difference between the drain and wakelocks on N4 & Jellybean and N5 & KitKat. Hopefully it's software only.
Anybody figured anything out with this? I am getting bluesleep and msm_serial_hs_dma wakelocks. I use a Pebble also.
Edit: Saw there was a thread for this on the Pebble forum and they apparently deleted it because I had to view a cached version.
Unfortunately, my Nexus 4 is out of commission for the time being but I did get some (not very conclusive) data that showed the issue is not preset with the N4 & Jellybean.
However, I found more information regarding the subject. I found this post on the pebble message boards that seems to confirm the issue lies mostly with the Pebble watch. I tested this by disconnecting my watch but leaving bluetooth on (both with it connected to nothing and on a half an hour drive with my N5 connected to my car). The wakelock is nowhere near as crazy as it is with the Pebble.
Doing more research on the bluesleep wakelock in general yielded a couple of results here in XDA ranging from missing binaries to kernel bugs. The fact that it's only happening to the Pebble is interesting however.
I wonder how other Bluetooth "smart" devices do with the Nexus 5. I don't own any other ones but if someone else does that would prove an interesting test.
Seeing the same thing. Got a Pebble yesterday and seeing the Bluesleep wake lock in BBS.
edit: wrong thread!
Has anyone been able to test this with another Bluetooth data device (ie: not a headset)?
Same Blue sleep issue
I'm having the same issue.
Running 4.4.1 with ART runtime.
Using Sony bluetooth headphones.
Over 2.5 hours of wakelocks today.
Wasn't an issue on 4.4 so must be software glitch in 4.4.1
Will need to post it to Android code database so it can be locked into.
almightywhacko said:
Has anyone been able to test this with another Bluetooth data device (ie: not a headset)?
Click to expand...
Click to collapse
Ketzal said:
I'm having the same issue.
Running 4.4.1 with ART runtime.
Using Sony bluetooth headphones.
Over 2.5 hours of wakelocks today.
Wasn't an issue on 4.4 so must be software glitch in 4.4.1
Will need to post it to Android code database so it can be locked into.
Click to expand...
Click to collapse
I have the same with Android 4.4.2 using ART: Pebble app has 4h 8m of keep awake on 6h 36m total. I found a fix for bluesleep wakelock for Motorola Atrix, probably someone could build one for N5.
I think that the wakelocks issue is related to ART; I switched back to Dalvik and now it seems working fine as before.
almightywhacko said:
Has anyone been able to test this with another Bluetooth data device (ie: not a headset)?
Click to expand...
Click to collapse
I have the same thing with my samsung gear smartwatch , a search for the issue brought me here
bluesleep
msm_serial_hs_dma
msm_otg
msm_serial_hs_rx
are the main problem wakelocks
dece27 said:
I think that the wakelocks issue is related to ART; I switched back to Dalvik and now it seems working fine as before.
Click to expand...
Click to collapse
I have same issue with dalvik runtime and pebble smart watch.
nexus_ix said:
I have same issue with dalvik runtime and pebble smart watch.
Click to expand...
Click to collapse
Same issue for me now, Galaxy s4 running GPE ROM on 4.4.4 with Pebble Smartwatch. Almost 100% awake due to BT. If I turn off BT thongs go back to normal ...
Any fixes yet?
Same problem with jawbone up24.
I have the same problem. Started when I installed the beta XY findit app for BLE tags.
I have uninstalled that now, but whenever I have bt open, the battery drains blazingly fast. no BT headsets or anything. I mostly use the bt to interact with iBeacons.
i have been having this issue a lot to. seems to be caused by my pioneer nav in my car. bluetooth does disconnect however bluesleep wake lock stays going until i turn off bluetooth. hasnt always been a problem. started maybe a month ago. very strange. running slim rom. happens with stock slim and elementalx kernels.
I have had this issue a few times with certain versions of Franco kernel. I have a Fitbit Flex that syncs with my phone.
I am causing battery drain after upgrading my phone to Android 5.0.2 - Nameless for Oppo Find 7.
My battery life shrinks from 2-3 days to 1.
I have actually mentioned much faster reaction, but battery life is on the edge of acceptance.
Do you have any idea, or similar experience?
Thanks a lot.
-Jan
jan.stanicek said:
Do you have any idea, or similar experience?
Click to expand...
Click to collapse
I have the same, less than a day on CM12 after 2 on KK. Bluetooth is screwed on CM12 for Togari though, I'm sure it'll improve once they fix it... Is bluetooth dodgy for your phone too?
What you mean - dodgy? Bluetooth works fine - with hands free at least. Even SW2 has much faster responses from phone comparing to previous Android versions.
I will ask creators of Nameless ROM then...
jan.stanicek said:
What you mean - dodgy? Bluetooth works fine - with hands free at least.
Click to expand...
Click to collapse
Bluetooth on mine stops working from time to time, and frequently needs a phone reboot to get bt audio working. As I say, that may be limited to the specific phone model.
Mine BT is quite stable - i have asked in forum here - http://www.oppoforums.com/threads/5-x-namelessrom-all-variants.22451/page-204#post-327785 . So lets see, whether someone pick up the topic ...
Has anyone experienced issues with Bluetooth devices? I have 2 devices (that are somewhat obscure) that I'm having problems with. First, what does work:
1) Beats Wireless Headphones
2) Bluetooth in my car
3) Unify Roverbeats (For bluetooth via A/V receiver that doesn't have it built-in.
4) Fitbit Surge (Had a little trouble getting it paired initially, but it's been fine since.)
The two items I'm having the trouble with are:
1) Omron 7 Series Wrist (BP654) Blood pressure cuff.
2) Vicks SmartTemp Bluetooth thermometer.
I have gotten both to pair, though it seems to be hit and miss. Once I need to actually use them, though, I'm having little to no success in getting the phone to see them. Unfortunately, I have to take both my BP and Temp every 3 hours (due to recently diagnosed, extremely rare immune system disorder.) This would be a deal-break for me, with the Blu Pure XL, it I didn't have 2 other android tablets I can use. However, I'd sure like to have these working on the phone! (BTW, they all worked seamlessly on my LG G4.)
Has anyone else experienced bluetooth issues with the Pure XL?
More Bluetooth problems....
The Bluetooth problems I mentioned earlier have only worsened. My car sometimes will, sometimes won't connect. The surge connects 90% of the time. Everything else is touch and go, with my BP Cuff only connecting once (during the pairing sequence.) Also, when selecting "un-pair" on any device already paired almost never un-pairs it. I usually have to reboot, then try again to actually get it to un-pair.
Aside from the Bluetooth issues, I've not really encountered anything else that is a show-stopper. I'd like to have Android pay, but it's not a necessity. I want root more (which disables Android pay anyway.)
DannyHammons said:
Has anyone experienced issues with Bluetooth devices? I have 2 devices (that are somewhat obscure) that I'm having problems with. First, what does work:
1) Beats Wireless Headphones
2) Bluetooth in my car
3) Unify Roverbeats (For bluetooth via A/V receiver that doesn't have it built-in.
4) Fitbit Surge (Had a little trouble getting it paired initially, but it's been fine since.)
The two items I'm having the trouble with are:
1) Omron 7 Series Wrist (BP654) Blood pressure cuff.
2) Vicks SmartTemp Bluetooth thermometer.
I have gotten both to pair, though it seems to be hit and miss. Once I need to actually use them, though, I'm having little to no success in getting the phone to see them. Unfortunately, I have to take both my BP and Temp every 3 hours (due to recently diagnosed, extremely rare immune system disorder.) This would be a deal-break for me, with the Blu Pure XL, it I didn't have 2 other android tablets I can use. However, I'd sure like to have these working on the phone! (BTW, they all worked seamlessly on my LG G4.)
Has anyone else experienced bluetooth issues with the Pure XL?
Click to expand...
Click to collapse
I've only paired a Metawatch so far but no issues. I keep forgetting to sync it to my car. I'd say the connection with the XL is better than with my M9, which dropped/reconnected randomly.
So far it seems to work fine with my car but when I use it with moto x sol deck it starts breaking up after 15-20 minutes. The only way to fix it is to turn on and off bluetooth.
Pure XL bluetooth serious problem
I have a Pure XL also, originally i only had problems occasionally with playing media through my LG Tone+ headphones. then i also tried connecting my Fitbit Charge HR it would shut down the bluetooth and lock the bluetooth off. i tried uninstalling the fitbit app and only running the headphones and the bluetooth ended up locking up. when i go to the bluetooth settings it shows it as constantly turning off and turning on. i cant stop it. tried rebooting. and also tried turning off and leaving off for awhile and still when i turn it back on it is still locked up.
Issues with jawbone up3, screwed up bad
Also having issues maintaining a sync without a reboot. In my wild attempts to fix this issue I ended up uninstalling Bluetooth Share.... Would any of you fine gentlemen be kind enough to post a copy of the apk from /system/bluetooth for me?
edit: found it github*com/acheron1502/android_vendor_BLU_BLU_PURE_XL/tree/master/proprietary/system/app/Bluetooth
thanks to acheron1502!
I only use Bluetooth for me FM transmitter in my car.... I never seem to have any problems at all as far as connection and playing music/sounds.... But the hands-free doesn't seem to work.... I can hear them but they can't really hear me very well.... I just put it off to the mic on the FM transmitter....
Just got my blu pure xl today and Bluetooth sucks, its not much better than my blu vivo air. Signal cuts off only being like 5 feet from the phone using my brand new jbl reflect mini Bluetooth earbuds. Hooked to my 4 year old kindle fire hd left on my second floor I was still getting reception in my basement. I'm so pissed I thought that this specked out phone would have good Bluetooth reception but nope ****ty. Blu/gionee needs to start putting way better Bluetooth transmitters in there phones.
I've got to reboot my phone several times a day to keep synced with my runtastic orbit. definitely the phone, had no issues with my LG. Its a nuisance, not a major issue.
Bluetooth woes followed by total meltdown!
After all of my initial issues with Bluetooth on my pure XL, I put a Samsung 200 GB MicroSD card in. It worked for a while, but I think I somehow damaged the card moving it in and out of the phone. Finally, I left the phone charging with card inserted. After an hour or two I came back to get it and it was fire hot...so hot that the plastic back cover had started to melt right below the memory card slot. After it cooled down I removed the SD card. The went on to work half the time, but eventually completely died. I contacted BLU and they sent me an RMA, so I sent the phone to them. I figured they would come back and say the phone was not covered anymore because I had the TWRP recovery and root installed. However, after they received the phone, I got an email with tracking number on the return to me. They ended up sending a completely new phone (off the shelf with all the goodies included.)
Since the new one has been back, and I got the march update, I haven't had any Bluetooth issues save 1: it won't connect to my Denon AVR receiver's Bluetooth mode. Everything else that I listed at the start of the thread is all working correctly now. Every once in a while I have to do a reboot to reset it, but it's way better than it had been!
BLUETOOTH CLICKING NOISE (handsfree)
Is anyone having issues with when using their BLU Pure XL in the car when using handsfree? I have an issue when about 1 minute into the phone call, the person I am talking to hears a loud click every 2 seconds and will not stop until I turn off the bluetooth or put on speaker. If i switch back to bluetooth, same thing happens. The longest I've gone on a call is probably 4 minutes before it started to happen. If i hang up and call the person back on bluetooth, same thing happens.
Anyone has a solution with this as its so bad that I am considering buying a new phone because of this issue!
Thanks