Wanted to post this in the actual development thread but can't due to post count. so here goes. I've been using the recently posted CM7 rom with bluetooth working. I've got no problem with turning the bluetooth on, and can even pair it with my Fascinate, although it says it's paired but not connected. I want to be able to pair it with my Fascinate and use the GPS from it, but so far Bluetooth GPS Provider just tells me there is a problem with the GPS and to restart it and try again. Am I wrong in thinking this should work? Do I need a completely separate bluetooth capable GPS?
clak84 said:
Wanted to post this in the actual development thread but can't due to post count. so here goes. I've been using the recently posted CM7 rom with bluetooth working. I've got no problem with turning the bluetooth on, and can even pair it with my Fascinate, although it says it's paired but not connected. I want to be able to pair it with my Fascinate and use the GPS from it, but so far Bluetooth GPS Provider just tells me there is a problem with the GPS and to restart it and try again. Am I wrong in thinking this should work? Do I need a completely separate bluetooth capable GPS?
Click to expand...
Click to collapse
Android doesn't support Bluetooth GPS directly. http://www.appbrain.com/app/bluetooth-gps-provider/de.mobilej.btgps
Per my original post, I'm already using that application, and it only tells me there is a problem and to restart the gps.
I cant even get BT to turn on for more then 2 sec with CM7 17,18 havent tried 19
Ive cleared the Cash and powered off by holding the power button, powered off from CM7, tried with wifi on/off cant seem to get it to work any suggestions?
I don't know, turning it on worked after a simple restart, I just can't get it to connect properly apparently.
I got Bluetooth GPS Provider to connect to my Holux GPSlim240. GoogleMaps is using the GPS signal perfectly. I also get the occasional restart msg but I think its the bluetooth moving out of its 2 to 3 foot range. Menu settings on Bluetooth GPS also seem weird. The GPSlim is a SiRF but when selecting that it seems to fail more. Used "other" in GPS type.
Friends ...... , HTC One it seems has a terrible Bluetooth range ....... I have a Logitech BoomBox (Bluetooth spks) and a Belkin Bluetooth receiver connected to my AVR. In both the cases, when connected to my HTC One it looses audio in just couple of feets. Specially with belkin receiver. But when I tested the same with my iPhone 4, it works perfectly, till the Bluetooth's designated range of 30 feet (10 meters) ... with both Belkin and Logitech ....
so it has something to do with HTC One's Bluetooth.
People with HTC One and having any Bluetooth audio device, please test this and report if you are also facing the same issue, Or is there something that I can try to increase the range. Its pathetic, 2-3 feets at the max. I am bitterly disappointed with this ..........
Regards.
Sammy
I think that Android 4.1 had a BT flaw that was fixed in 4.2.
so this means its more of an android issue than HTC One........ any alternatives to improve this, till we have an 4.2 update
I was using bt audio yesterday and it was horrible. I did some googling, try turning off wifi before you connect to the speakers, it solved my trouble straight away. I found if the music was playing when I turned wifi back on it would still be ok. Might help?
jiggle_ said:
I was using bt audio yesterday and it was horrible. I did some googling, try turning off wifi before you connect to the speakers, it solved my trouble straight away. I found if the music was playing when I turned wifi back on it would still be ok. Might help?
Click to expand...
Click to collapse
Jiggle .... my friend, you made the day for me, how so ever strange may it seem, it did work .... ..... I switched of my wifi and then connected Bluetooth to Belkin receiver and vola!! :victory:... no drop outs and was able to use BT at full 30 feets, and then if I switch on the wifi later all is well.
Strange, if wifi is working before I connect BT, it drops and is very uneven ......... must be some bug, but anyway, solution is not as irritating as one might expect.
Thanks again Jiggle, for you input, saved me a great disappointment.
Regards
Sammy
sam9s said:
Jiggle .... my friend, you made the day for me, how so ever strange may it seem, it did work .... ..... I switched of my wifi and then connected Bluetooth to Belkin receiver and vola!! :victory:... no drop outs and was able to use BT at full 30 feets, and then if I switch on the wifi later all is well.
Strange, if wifi is working before I connect BT, it drops and is very uneven ......... must be some bug, but anyway, solution is not as irritating as one might expect.
Thanks again Jiggle, for you input, saved me a great disappointment.
Regards
Sammy
Click to expand...
Click to collapse
whew you had me in a panic here. (o; I'm still a little traumatized from my asus T201 wireless issues.
The Wifi/bluetooth issue is a drawback of the aluminum body design of the One. Bluetooth shares an antenna with wifi transmit. I believe wifi receive shouldn't interrupt bt though.
Then there should also be a problem if I switch on wifi after I connect BT. ,... in which case it works. It only creates a problem, if the wifi is first on and then I connect BT. ...... which is strange
Just for information. I had 3 htc, desire hd, sensation, onex and ALL had problem with bluetooth, weak signal, using a headset with the phone in my pocket already failed. I now have a note2 and this problem does not occur, being used in the same situation. So ....
sam9s said:
Then there should also be a problem if I switch on wifi after I connect BT. ,... in which case it works. It only creates a problem, if the wifi is first on and then I connect BT. ...... which is strange
Click to expand...
Click to collapse
My m7 (TrickDroid, elementalX 0.11 default overclocking and undervolting) is having the BT issue whenever wifi is on, regardless of whether I connect the BT device while wifi is off, and regardless of whether audio is playing when the wifi is turned back on. In other words, on my device, BT really really sucks if wifi is connected, period. Any suggestions other than not to use wifi if I want to use BT?
Update: My router (Netgear wnr2000v3) seems to use 2.4 Ghz channels. Any thoughts about whether swapping the router with a dual-band or 5 Ghz channel router would work around this issue?
pcadvocate said:
My m7 (TrickDroid, elementalX 0.11 default overclocking and undervolting) is having the BT issue whenever wifi is on, regardless of whether I connect the BT device while wifi is off, and regardless of whether audio is playing when the wifi is turned back on. In other words, on my device, BT really really sucks if wifi is connected, period. Any suggestions other than not to use wifi if I want to use BT?
Update: My router (Netgear wnr2000v3) seems to use 2.4 Ghz channels. Any thoughts about whether swapping the router with a dual-band or 5 Ghz channel router would work around this issue?
Click to expand...
Click to collapse
I did pick up a new dual-band router and set up the phone to connect only on the 5Ghz band, and it worked! No more bluetooth issues at home. So if you run into this issue, a temporary workaround until (hopefully) HTC/Google provide a fix is to avoid the 2.4Ghz band.
Strangely enough, my Bluetooth range keeps decreasing with each software update. When I first bought this thing, I was generally impressed with how far I could walk from my BT speakers. Not as good as my evo 4g or 3d, but decent. Better than my gs3 and gn2.
Now I tend to make it about 5 feet or so with minor cut-outs while using apt-x. If I put my hand between the signal at 10ft, I can stop it completely. If I touch the upper-right of my phone with my thumb as I hold it in my right hand, I can kill the signal as well. Very much an antennagate going on here just like the iPhone 4.
This phone (stock, non rooted) was working with BT fine under 5.01and Kit Kat before it for mostly calls. I know it is the phone because I have tested it now in three different cars, my 2014 Prius, a new Chrysler and Ford. It exhibits the same behavior. Pairing is not a problem. If the screen in on when I enter the car the connection is made. When the screen dims (sleeps) the connection drops shortly thereafter. If I swipe and get the screen back on I can manually re-connect through the car's radio. If I enter the car with the phone in my holster, likely asleep, it will not connect.
Keeping the screen from sleeping appears to "remedy" this issue but that is hardly an option in terms of battery life. Normally I keep the phone in a holster and never had this issue. I have tried every remedy on the Internet. I am using safe lock and have the radio as a trusted device. I have removed safe lock and the same issue ensues. I have unpaired, cleared cache, re-paired etc.
last night I hooked up the phone to my Garmin Nuvi via BT. No disconnect issues.
Any suggestions on further troubleshooting? Any advice on this problem would be greatly appreciated. Thanks..
Work around found
I found an app called Bluetooth keepalive. It appears to have solved my problem for now. Since installing it the connection has not disconnected. The app uses very little battery power
Colvinhurst said:
I found an app called Bluetooth keepalive. It appears to have solved my problem for now. Since installing it the connection has not disconnected. The app uses very little battery power
Click to expand...
Click to collapse
what kind of car do you have? you might wanna look into updating software in your car or at least try it with another phone (preferably the same) just to rule it out
Hey guys!
I have a few problem with my P9.
First of all the wifi keeps disconnecting all the time. It says connected for like two seconds, then disconnects, then reconnects immediately, disconnects again, reconnects ... and so on.
I've tried various firmwares and different wifi networks, but the problem persists. GPS and bluetooth seem to be working properly though.
Does anyone know a possible fix?
Another problem is that the loudspeaker sounds distorted, like a crackling sound. Sometimes it stops completely.
Apart of these problems it works fine.
Both of the problems might be because of a water damage, so now I'm wondering ...
Does it make sense to replace just the wifi antenna and the loudspeaker part?
Those would be cheap, so I'd consider replacing them myself.
Or could it be a problem with mainboard or sub board?
In this case I would rather go for a new phone.
I'm not sure, if I wanna take the risk. What's your guys' opinion?
Hey guys, Merry Christmas!
Out of the blue as I was riding my bike somewhere with GPS on and Bluetooth connected to my speaker everything was going fine.
I got where I supposed to be, the connection was fine and all.
When I wanted to return though, the Bluetooth speaker just wouldn't connect.
I tried turning both the speaker and the phone on and off but nothing changed.
Messed a bit with the developer settings but again nothing changed.
Tried to connect to a few more speakers I have and none connected.
My BFF has the same device and his device connects just fine to my speakers, my device just refuses.
It does *technincally* connect but it says Connected (no media), which is obviously useless in my case because the audio players from the phone's speakers and not the external ones.
For some weird reason, it does connect and play though to my car's Bluetooth. (Seat Ibiza 2020 MY not as it matters)
I changed a few roms and one weird thing I noticed when I was running POSP I think was in the dev options, Bluetooth mode, everything was greyed out besides default.
That's pretty weird if you ask me, I mean SBC AAC and some others *should* be available right?
So my concern is I'm facing a firmware/hardware issue, unfortunately, maybe some persist.img problem?
I ended up flashing with mi flash tool the latest miui 12 europe and global roms without luck, and now I'm in the middle of flashing the Chinese one just in case.
Has anything similar happened to you?
How did you fix it?
I cannot for the life of me find a solution and think about giving up and sending it for repair.
Well after trying lots of roms and whatnot (I even went back to MIUI 10, Android 9) I found out that If I try to connect with my speakers as the first device it won't connect, if I connect to my car or my Airdots and then try to connect to my speakers then it does indeed connect.
I cannot comprehend why this behaviour exists, but at least it is persistent if I don't reboot and I only need to this on the first pairing.
I guess problem solved...?
(it should be able to connect normally, but that workaround is good enough I guess)