I know, my question seems so elementary.
I do know how to turn it on and all that, but I just can't seem to get it to work.
It says that it's on, but whenever I scan a bluetooth enabled device like a mobile phone or my PC that has bluetooth (and they're discoverable), the NC just can't detect them and vice-versa.
I even tried using the 'Bluetooth File Transfer' app found on the market but it didn't do anything different.
I could be missing something though. Care to point it out?
Actually this seems like a misfunctioned BT.U should see right away all BT devices around.Are they close enough to be discovered?
Did U try with other Rom's?
I think you first have to turn on Bluetooth, then reboot. At least at some point this was the case.
It also may help to reboot with wifi and bluetooth off, then turn on only bluetooth as fast as you can once the reboot is complete.
Sent from my DROID2 using XDA Premium App
It was a pain in the neck, don't know if it gets any better or still pain in the axx.
Anyway, let just start from point zero.
1. Assuming NC is on, turn off wifi
2. Reboot NC
3. Turn on blue-tooth
4. Turn on wifi
After that, expect 1/2 hours (and/or pulling your hair, scratching your head) try to sync (pairing) the 2 devices. Even if they see each other and successfully paired, there was (I use the past tense) no guarantee that they would connect together.
the range of our NC's BT is less than a foot so make sure your phone is basically laying on top of the nook when youre trying to sync.
Related
Every phone I have had, where it had bluetooth, had the ability to turn off discovery. On this WP7, I only see the on/off switch for bluetooth. I thought that discovery on all the time ran the battery down faster. And if left on made the phone vulnerable to attack by ne' er-do-well's.
I think pairing with a headset is the only thing you can do with WP7 right now. There's no file transfers or anything else. I just turn it off when I'm not paired.
wildbilll said:
Every phone I have had, where it had bluetooth, had the ability to turn off discovery. On this WP7, I only see the on/off switch for bluetooth. I thought that discovery on all the time ran the battery down faster. And if left on made the phone vulnerable to attack by ne' er-do-well's.
Click to expand...
Click to collapse
I think you are write WildBill, the BT logo on the home screen does not allow you to click it and turn BT off.
Unless I am wrong, you have to go into settings everytime.
As being discussed in various threads, some people are having BT problems with EB13 based ROMs.
The Problem
Inability to connect at some future time after having paired device with phone. Rebooting doesn't help. Only solution is to unpair, and re-pair, then device will both pair and connect with phone.
Also seen by some people are audio routing problems after disconnecting BT. Not sure if this is confined to devices that support (and connect) A2DP... more investigation/testing needed.
The Workaround
I tested various conditions to see how the BT subsystem behaved under various usage modes. In particular, across boots, turning BT on and off on the phone, on the device, etc. -- and then observed if automatic connection would re-establish after each combination of conditions.
I found that the problem seems to only happen if I turn off BT on the phone. If I leave it on, pair and connect with a BT device, then I can turn the device on and off at will, and it will automatically connect.
This (normal) function persists across reboots, at least for the few I tested.
I don't know how power-hungry the BT radio is when idle and not connected. My gut feel is that it is a pretty small drain, so leaving BT on all the time as a workaround probably won't have much of an impact on battery drain. I use Juice Plotter, and have a good history with BT off to compare to. I'll post JP measurements/results tomorrow after a 24 hour cycle.
Caveats
I also changed my Epic BT device name before I explored this situation with toggling the BT radio on the phone. While the name change did not correct the problem on its own, I can't rule out that the combination of name change and leaving BT on is what is making things work, rather than just the latter alone. So, to try this workaround, you must also change your BT device name on the phone, and leave BT on. Then, clear pairing and re-pair for the target BT device.
My Request
Would people that are having this problem please try this out, and report back in this thread success/failure, and any other observations. What we see in testing these different modes will be very helpful to the devs in trying to trouble-shoot an fix this problem (which I have no doubt they will long before Samsung does).
It should be noted that some folks are having issue connecting to a device, even after un-pairing and re-pairing. If that is the case, you might try this-
http://forum.xda-developers.com/showpost.php?p=12120496&postcount=1392
Also, some folks are reporting an issue with multiple pin requests before a device will finally pair. I haven't seen that one myself, but just thought I'd mention it.
For what it's worth, other than the BT routing issue, I haven't seen any of these pairing or connection issues on my stock rfs Epic. It wasn't until I converted my other Epic to ext4 that Bluetooth had any issues, and they were all fixed by wiping data and have not returned since.
I have tried the workout around before in the past, and it changed nothing. Also I have noticed I seem to have more issues with particular audio bluetooth ear pieces, like BlueAnt Q2. It will show pairing is connected but after a couple hrs on the bluetooth connection is gone, but like I said it shows paired. My cheaper Plantronic ear pieces seem to work much better, except the fact I have to re-pair after each reboot of the Epic.
Ive tried leaving bluetooth on all the time, but after a reboot,
i have to repair ive tried all suggestions to fix it and the only way it seems is once it gets connected is always have the phone on and cant die and bluetooth always has to be on,
even after a long period of time somehow it loses the connection even if bluetooth is on and phone stays on,
There must be somethng the developers can patch with a flashable fix or another work around to get squash this annoying bug.. ill try to get a logcat today and try your method again see if i have luck
I will try to leave mine on and see what happens. Name change did not help.
But short on time. But given the chance I want to go back to bonsai 3.0.1 and see if I have the same problem. I don't recall it giving me a problem.
Edit: of I leave BT on, on the phone and just turn the BT device on/off it will not pair back up.
Edit: May have figured something out. I have been toggling BT with a widget. When I toggle from the notification bar it seems to work (so far). Which would also explain why it quite working as I added apps. As from clean install is used the notification bar and later used my power widget. But I have always used a widget before. I will test this out at work and see if this work around keeps working for me.
Sent from my SPH-D700 using XDA Premium App
I have to re-enter the PIN after every reboot. Mildly annoying.
Having tried the various bluetooth fixes given in different posts, I am now just leaving bluetooth on as described in the workaround above. I have left it on for a couple of days now and have had no trouble whatsoever with my headsets (both regular and stereo/A2DP). They connect as they should and do not require re-pairing. Even if I reboot my phone they have been connecting back up without issue. The only thing I cannot do is manually toggle bluetooth off and back on or the devices need pairing again.
I initially was worried about battery life by leaving BT on, but so far I have not seen any major difference... is the bluetooth radio only consuming power if a device is connected?
I still hope a permanent fix can be found for this as it makes me feel like my phone is "broken" somewhat
BTW, I am running EB13 with CWM 3.0.0.6, Bonsai 3.0.1, and Emotionless Beast theme
automator said:
Having tried the various bluetooth fixes given in different posts, I am now just leaving bluetooth on as described in the workaround above. I have left it on for a couple of days now and have had no trouble whatsoever with my headsets (both regular and stereo/A2DP). They connect as they should and do not require re-pairing. Even if I reboot my phone they have been connecting back up without issue. The only thing I cannot do is manually toggle bluetooth off and back on or the devices need pairing again.
I initially was worried about battery life by leaving BT on, but so far I have not seen any major difference... is the bluetooth radio only consuming power if a device is connected?
I still hope a permanent fix can be found for this as it makes me feel like my phone is "broken" somewhat
BTW, I am running EB13 with CWM 3.0.0.6, Bonsai 3.0.1, and Emotionless Beast theme
Click to expand...
Click to collapse
In my experience, the BT radio does not use any power when not connected to a device. If it does, it's not noticeable in Spare Parts or in performance.
I fixed my connection problem by doing a wipe and fresh install of my current rom. Now my bt is working perfect. Just make sure not to recover your date from nandroid that may cause u to recover what ever was causing the bt problem just restore your apps only my back up or appbrain.
Sent from my SPH-D700 using XDA Premium App
blackdragon79 said:
I fixed my connection problem by doing a wipe and fresh install of my current rom. Now my bt is working perfect. Just make sure not to recover your date from nandroid that may cause u to recover what ever was causing the bt problem just restore your apps only my back up or appbrain.
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
What rom are you running?
Also did anyone by wiping data all data, confirm that on bonsai rom fix the non connecting issue?
Have the pairing issue with ACS EB13 Frozen ROM 1.0.3/ Twilight kernel. The BT headset I use is Plantronics 975. Never had a problem with any of my phones until now... even my Treo 755 connected properly, not to mention BB Tour FWIW, my headset supports A2DP and I wiped/reflashed ROM/kernel several times without resolving the BT issue. Will leave BT on, but does it mean after every reboot I have to re-pair? That's not good if true, I hope a permanent fix can be found soon.
davidrules7778 said:
What rom are you running?
Also did anyone by wiping data all data, confirm that on bonsai rom fix the non connecting issue?
Click to expand...
Click to collapse
I'm using syndicate frozen
Sent from my SPH-D700 using XDA Premium App
Update: For me at least, this workaround is still working 3 days later without a hitch, and across more reboots than I can count.
While I don't _know_ with tech/spec/engr certainty, as mentioned above it seems that BT uses negligible power when it is only listening for connection requests, and has had no discernible impact on battery drain at all.
So, this seems to be a viable workaround for the time being for some of us... it's real. What we need to work on as a community is figuring out what the critical difference is between those for which it works, and those for which it doesn't. KEEP POSTING AS MUCH DETAIL AND INFO IN THIS THREAD AS YOU CAN, EVERYONE... DATA IS WHAT WILL GET US TO THE BOTTOM OF THIS.
Personally, I think the key difference between the two groups is the size of your junk -- People with small equipment seem to be having all the failures
Sent from my mind using telepathitalk
I've had this issue on all Froyo builds. I have tried 7 different BT headsets from Samsmsung, Plantronics, Jabra & Blue Ant, all of them a2dp compliant with the same result, after a while, they stop connecting and I have to re-pair. As for the "workaround" since I have several extended batteries I've never turned BT off, and while it does take much longer to lose pairing, it eventually stops syncing or syncs only the headset protocol but not A2dp. For myself, the only solution I've found is to go back to DI18 which, although has its faults, works flawlessly with BT
I have been trying to get my brother's Epic working properly. It is rooted with EB13 installed. If this bluetooth error is not related to what others are having, let me know and I will create a different thread. I got his motorola H520 paired. I press the button and it starts the bluetooth voice dialing. It beeps and says please speak and then immediately gives and error saying the connection to the bluetooth was lost but the settings shows it to still be conneceted and it is as you can answer calls with the bluetooth without having to reconnect it.
My plantronics backbeat is paired and for phone calls is working, but sometimes no audio through music or video players. I had to un-pair, then re-pair then audio will work for a while.
I am using CWM 3.0.0.6 with midnight ROM with its installed kernal
Happening on my Plantronics Voyager Pro+ - It seems that everytime I pick up my phone the BT disconnects and then after about 15 to 30 seconds reconnects as long as I don't push any buttons.
There is also a lag "thingy" that occurs when I'm on a call and then another person calls - while the the second call is coming in, it seems like the packets get interrupted from the handset to the headset. Then once the incomming call goes to VM, the audio from the current call gets restored. Not sure if this is helpful or not, but I wonder if there are some routines in the BT transmission that have common "hooks" which are used when a second call comes in - Hope that is not too much of a noob statement...
Is anybody else having that "laggy" issue in the same circumstances?
I have had this problem even from android 3. My xoom will randomly open to lock screen, and if I don't see it it will stay there and drain it's battery. Is there a way to make it close the screen again automatically, or even prevent it from opening? I have tried everything, shutting down wifi completely (for notifications) among others.
i have same issue
Do you have a bluetooth headset connected to your device. Mine would turn on by itself if I left and active bluetooth device attached. Once I started turning of the bluetooth antenta regularly this stopped happening for me.
To tell you the truth I do have my iphone connected to my xoom via bluetooth but the bluetooth feature is off at all times except for when I need it (for teathering purposes). I just checked again and it is off (since months that I opened it last time) both on mobile andxoom. I will delete the pairing though and hope for the best.
Any other suggestions?
So, for some reason, my Bluetooth doesn't function properly as it should, which is weird, since my phone is still on stock, and the only modifications I've made are unlocking the bootloader and rooting the device. I also installed Power Toggles, but I don't think that's the issue at hand.
Pretty much, whenever I turn the bluetooth on, it tries for a while to turn it on, then gives up and won't let me turn it on. At that point, I have to restart the phone, and when it reboots back up, the bluetooth is on without me having to start it up. Then it works properly, but if I wish to use the bluetooth again the next day, I have to repeat the process of rebooting the device. Any ideas?
I had this issue when I Downloaded a FM radio app from the Play store to see if it would work. I just deleted the app. Went into safe mode then into normal mode and it fixed it.
Don't know what you case can be. But you can try going into safe mode and back to normal and see if there are any different results.
Sent from my Nexus 4 using Tapatalk 2
I had this same problem after installing Torque, and using it with default settings that auto-enabled/disabled bluetooth. After turning all that crap off it is back to normal.
I use bluetooth for audio playback and an hf/A2DP headset dialing via Motospeak, as well as Torque with a bluetooth odb2 interface, and it all works perfectly since disabling Torque's auto-bluetooth settings. My only issue is that it takes Motospeak a bit long to restore audio playback after a hf call command.
I would look for an app that you have that is the controlling bluetooth on/off.
I wonder if it isn't a software bug. I have the same issue but I don't have any apps that are causing the issue of atleast from what I can tell. I'm also unlocked and rooted.
I removed Bluetooth from Power Toggles. It's been two days and all seems well. Now we wait.
yahoowizard said:
So, for some reason, my Bluetooth doesn't function properly as it should, which is weird, since my phone is still on stock, and the only modifications I've made are unlocking the bootloader and rooting the device. I also installed Power Toggles, but I don't think that's the issue at hand.
Pretty much, whenever I turn the bluetooth on, it tries for a while to turn it on, then gives up and won't let me turn it on. At that point, I have to restart the phone, and when it reboots back up, the bluetooth is on without me having to start it up. Then it works properly, but if I wish to use the bluetooth again the next day, I have to repeat the process of rebooting the device. Any ideas?
Click to expand...
Click to collapse
This happened to me as well
Sent from my Nexus 4 using xda app-developers app
strobex said:
This happened to me as well
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Similar problems here, the weirdest thing is idk which app causes that. Because I didnt install that much. Only thing I notice is it happened when the wifi is on.. Does anyone have similar problem??
Same problem here. I have a lot of apps but none I can think of that do anything with Bluetooth.
Sent from my Nexus 4 using xda app-developers app
yahoowizard said:
I removed Bluetooth from Power Toggles. It's been two days and all seems well. Now we wait.
Click to expand...
Click to collapse
Nope, still doesn't work.
Try going into safe mode.. See if it works, and then go back to normal mode.
Sent from my Nexus 4 using Tapatalk 2
Nothing yet? I'm just curious as to whether it's just a few people experiencing this, or a lot, since there doesn't seem to be that much talk about it.
I use Bluetooth everyday on my way home from work just to connect to my Bluetooth headset. Out of 14 days I may get one day where I turn Bluetooth on that I don't have to reboot for it to work.
Sent from my Nexus 4 using xda app-developers app
So we're on 4.2.2, I've went through safe mode and back a few times, and I've uninstalled and installed applications having to do with the Wi-Fi. Problem still seems to be there. It's just somewhat of a hassle to have to power down my phone completely, then start it back up, everytime I get into my car. I feel a hard reset mighttt fix the issue, but just looking for another way as of now.
My phone also have the same problem.. the bluetooth won't turn on.. stock 4.2.2 locked bootloader and not root yet.. anyone has a solution..
In last 2 weeks, I have "hard time" to turn the wi-fi on. Sometimes turn on and sometimes do not. It does not matter of what rom I am using, I still have the problem. Is my phone going to sh..?. Thanks.
cuiltheory said:
In last 2 weeks, I have "hard time" to turn the wi-fi on. Sometimes turn on and sometimes do not. It does not matter of what rom I am using, I still have the problem. Is my phone going to sh..?. Thanks.
Click to expand...
Click to collapse
You have rooted my touch 4g?
Sent from my HTC Glacier using xda app-developers app
cuiltheory said:
In last 2 weeks, I have "hard time" to turn the wi-fi on. Sometimes turn on and sometimes do not. It does not matter of what rom I am using, I still have the problem. Is my phone going to sh..?. Thanks.
Click to expand...
Click to collapse
More information would be necessary to tell you that.
- Do you see APs?
- Is the reported signal good?
- When you connect, does it connect at all or indicate a failure?
- If it connects, does it drop and reconnect continuously?
- Does it work on open APs with no security?
- Did you install any items that modify your wireless properties (like PMR?)
- Did you try with stock and see if it connects more quickly?
There are lots of potential issues totally aside from your WLAN radio failing.
The problem that I have is that in cm10 roms ( try few) the wi-fi slider sometimes is highliter and will turn on and sometimes will not be highlater and will not turn on. I went back to GB rom original and in Sense, I can turn on, but with error. It happen about 2 weeks ago and ever since, I have that problem. I can not remember what I did at that time, but I did not :mess: with radio. I did took the back cover of ( try to fix the sound). Did I mess up something there?. Look like the wi-fi acting up and will turn on when want to - I got nothing to say - just like my ex.
I decided to use some "bad" words against my phone and the wi-fi turn it self on. I am not joking. Go figure. The problem that I see - I can not use those kind of words in public.
I think that my phone is going to sh...
cuiltheory said:
The problem that I have is that in cm10 roms ( try few) the wi-fi slider sometimes is highliter and will turn on and sometimes will not be highlater and will not turn on. I went back to GB rom original and in Sense, I can turn on, but with error. It happen about 2 weeks ago and ever since, I have that problem. I can not remember what I did at that time, but I did not :mess: with radio. I did took the back cover of ( try to fix the sound). Did I mess up something there?. Look like the wi-fi acting up and will turn on when want to - I got nothing to say - just like my ex.
Click to expand...
Click to collapse
Hmm. If you're having that happen on stock, that's not good.
Okay, so you did something to it mechanically two weeks ago for sound issues and then your radio started to act up? When you say 'back cover', do you mean just popping the battery cover off, or taking it apart to fix connections? Perhaps something got knocked loose or unseated?
I did remove the motherboard cover to get to the speaker. I think that my have mess up something. Time for new phone any way. Thanks.