Hope I'm not duplicating anything, but there seems to be a lot of BT related questions and none answered in one unified place. Also I think the BT Dev thread should be left to the devs (to keep it easier for them to work on things, rather than help us mere mortals ).
This applies to CM7 (latest nightlies, Tablet Tweak RCs) ONLY (as far as I know).
So, if bluetooth does not turn on, there a few things that you can try.
Do a HARD reset (that is, hold down the power button until the NookColor turns off, then start it back up.
Fix Permissions in ClockworkRecovery:
Boot into CWR (w/SD, load it in. With CWR installed on eMMC, go to ROM Manager > Reboot into Recovery. Alternatively, hold down the power plus "N" button for ~8 seconds (from a shutdown NookColor).
Try both!
An interesting thing to note is some users (myself included) can only start up bluetooth within a pretty short window of time after the NC has booted up. Not sure why timing is important, but could be a factor for those who cannot start up BT after some given time of operation.
I found this tip that may work after a fresh (read: wipe system/data) install, but may also work after flashing a nightly over a nightly.
If you're ready to turn on Bluetooth, there's a trick. If you don't do this, Bluetooth will just refuse to turn on / be enabled.
Turn off wifi (Settings > Wireless & Networks > Wi-Fi)
Reboot
Turn on Bluetooth (Settings > Wireless & Networks > Bluetooth)
Turn on wifi
It seems a bit odd, but that's what you have to do. From then on out it'll work fine.
Click to expand...
Click to collapse
Credit here (step 2)
For a list and description of devices that work with the NC, check this out:
Known functional Bluetooth devices
For tethering data via BT, try android-wifi-tether. While it can be used to create an access point on your phone via wifi, you can also opt to use BT to create the tether. This works well in conjunction with TetherGPS which I use to provide GPS info to the NC from my G1 while using CoPilot Live to show navigation (I don't have data on the G1).
If you have the BT enable problem try this kernel and let me know if it changes anything:
http://forum.xda-developers.com/showpost.php?p=12683824&postcount=1754
dalingrin said:
If you have the BT enable problem try this kernel and let me know if it changes anything:
http://forum.xda-developers.com/showpost.php?p=12683824&postcount=1754
Click to expand...
Click to collapse
Tried that previously and it did not work for me.
In other words, it works as with all the kernels I've tried (your OC'd and stock kernel): it will start up if I start is quickly, but otherwise not.
ace7196 said:
Tried that previously and it did not work for me.
In other words, it works as with all the kernels I've tried (your OC'd and stock kernel): it will start up if I start is quickly, but otherwise not.
Click to expand...
Click to collapse
me too. I went back to 4/4 since them. If I leave BT on all the time, it is on when I boot, but if I turn off BT and reboot, it won't come on without a hardboot (holding down power.)
Fix permissions is NOT needed, just a hard boot.
dalingrin said:
If you have the BT enable problem try this kernel and let me know if it changes anything:
http://forum.xda-developers.com/showpost.php?p=12683824&postcount=1754
Click to expand...
Click to collapse
For the last few days Ive been trying to get BT working w/ my car stereo, using phiremod 5.3
I have no problems enabling Bluetooth (first time I had to reboot a few times and fix permissions)
With it flat against the stereo, I'm 'paired but not connected' and getting it to actually connect usually takes 4 - 5 tries.
After its connected- when I try to play any kind of music, it gets stuck every few seconds- and stays stuck for more than a few seconds (like 10) and plays again.
I just downloaded this kernel, (wiped caches, fixed permissions again) and it connected on the second time, and only got 'stuck' once for maybe 2 seconds, and played the rest of the song with no problems.
Seems like it changed something on my end...
Just figured I'd mentioned it.
(I can go back to the other kernel, or a different version of cm7, and see if I get the same connecting/ stuttering problem, if you thing it would help)
Btw- thanks so much for sharing all of your hard work!
breebauer said:
After its connected- when I try to play any kind of music, it gets stuck every few seconds- and stays stuck for more than a few seconds (like 10) and plays again.
I just downloaded this kernel, (wiped caches, fixed permissions again) and it connected on the second time, and only got 'stuck' once for maybe 2 seconds, and played the rest of the song with no problems.!
Click to expand...
Click to collapse
I dont' know if anyone who's building from source wants to take a look at this patch committed 3 days ago on the omapzoom tree to frameworks/base, but it seems to address a bluetooth corruption problem.
Can anyone who's using the copilot app tell me exactly how to get it set up? I can get the GPS signal to the nook but then I get an error about an invalid imei number.
Sent from my NookColor using Tapatalk
Calla969 said:
Can anyone who's using the copilot app tell me exactly how to get it set up? I can get the GPS signal to the nook but then I get an error about an invalid imei number.
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
Check out this posting:
http://forum.xda-developers.com/showthread.php?t=1024963
I believe you also need the Bluetooth GPS Provider app from the market.
Calla969 said:
Can anyone who's using the copilot app tell me exactly how to get it set up? I can get the GPS signal to the nook but then I get an error about an invalid imei number.
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
Never had an issue with the IMEI number, but here's how I got it setup.
Start with the TetherGPS app running server on the phone and client on the NC, as well as tether-wifi from google running on the phone, then connect to the AP on the NC
Next, open/install the app. It should read the GPS data from the phone
Now, switch back to a wireless connection with internet access, download the voice, then enter the serial/etc...
Finally, load the app back up after all the registration stuff 'n things, and use the "internet" connection from the phone to grab the GPS info.
Copied and edited from cm7 user thread.
I have xoom bluetooth keyboard with disconnect issues. Would the special kernel help with this?
From the accessories thread. "I found a work-around. Download the app Bluetooth Keyboard JP, change the settings in settings > Language and Keyboard to that app, then connect the keyboard." Anybody else try this or others? Blue Input is another one. I know of one more but can remember its name.
I'm running Phiremod v5.3 cm7 from emmc and cm7 nightlies from sd card. I usually have a data sd card but can switch it out. I have updated the cm7 sd card before. Not sure which nightly and OC I used last. Could use ClockWorksMod to flash this kernel to Phiremod v5.3. Could replace the kernel, uImage, on the SD card. Usually there are different kernels for emmc and sd card.
Another issue: When I have the keyboard active and playing flash files from the internet, it seems to buffer more. If I move the keyboard out of range or use settings to disconnect the keyboard, the buffering is less and the flash files play better. I have cyfi bluetooth external speakers. When I use them I get the same buffering issue, so I just use an external player through the headphone jack instead.
ace7196 said:
Never had an issue with the IMEI number, but here's how I got it setup.
Start with the TetherGPS app running server on the phone and client on the NC, as well as tether-wifi from google running on the phone, then connect to the AP on the NC
Next, open/install the app. It should read the GPS data from the phone
Now, switch back to a wireless connection with internet access, download the voice, then enter the serial/etc...
Finally, load the app back up after all the registration stuff 'n things, and use the "internet" connection from the phone to grab the GPS info.
Click to expand...
Click to collapse
Question: will 'Wireless Tethering' work in place of 'tether-wifi'? Or does it -have- to be 'tether-wifi'? Thanks!
any software will work that tethers.:-D
ace7196 said:
Never had an issue with the IMEI number, but here's how I got it setup.
Start with the TetherGPS app running server on the phone and client on the NC, as well as tether-wifi from google running on the phone, then connect to the AP on the NC
Next, open/install the app. It should read the GPS data from the phone
Now, switch back to a wireless connection with internet access, download the voice, then enter the serial/etc...
Finally, load the app back up after all the registration stuff 'n things, and use the "internet" connection from the phone to grab the GPS info.
Click to expand...
Click to collapse
Apparently the latest version of Copilot has introduced this error. I have spoken with tech support regarding the issue and they told me that they are aware of the problem and will release an update early next week that will fix the problem. Apparently if you have version 8.2.504 it works, but the new version breaks it. The dev won't send me a copy of the old version, so I guess I'll just have to wait and hope.
lschroeder said:
Copied and edited from cm7 user thread.
I have xoom bluetooth keyboard with disconnect issues. Would the special kernel help with this?
From the accessories thread. "I found a work-around. Download the app Bluetooth Keyboard JP, change the settings in settings > Language and Keyboard to that app, then connect the keyboard." Anybody else try this or others? Blue Input is another one. I know of one more but can remember its name.
Another issue: When I have the keyboard active and playing flash files from the internet, it seems to buffer more. If I move the keyboard out of range or use settings to disconnect the keyboard, the buffering is less and the flash files play better. I have cyfi bluetooth external speakers. When I use them I get the same buffering issue, so I just use an external player through the headphone jack instead.
Click to expand...
Click to collapse
I don't know if that is a solution, but the problem appears to be a conflict between wifi and bluetooth. Turn off wifi and most of your keyboard problems will go away.
Also there is an app on the market called "Null Keyboard" Which simply turns on a keyboard device that disables everything keyboard related. It doesn't disable bluetooth input, but it gets rid of the long-press pop ups and is suppose to solve other issues as well (including the software keyboard popping up every time you want to type.)
I haven't had time to install it, but it's purchased.
Does anyone know where (on the Nook) the BT chip/antenna is located?
It might help to know, since the range is so limited...
breebauer said:
Does anyone know where (on the Nook) the BT chip/antenna is located?
It might help to know, since the range is so limited...
Click to expand...
Click to collapse
http://www.zdnet.com/photos/nookcolor-teardown/487636?seq=62&tag=content;photo-frame#photo-frame
So across the bottom and up the right side as you hold it portrait.
khaytsus said:
http://www.zdnet.com/photos/nookcolor-teardown/487636?seq=62&tag=content;photo-frame#photo-frame
So across the bottom and up the right side as you hold it portrait.
Click to expand...
Click to collapse
Thanks! That makes a big difference...
(For some reason, I was thinking it was on the upper left corner- not sure why)
chisleu said:
I don't know if that is a solution, but the problem appears to be a conflict between wifi and bluetooth. Turn off wifi and most of your keyboard problems will go away.
Also there is an app on the market called "Null Keyboard" Which simply turns on a keyboard device that disables everything keyboard related. It doesn't disable bluetooth input, but it gets rid of the long-press pop ups and is suppose to solve other issues as well (including the software keyboard popping up every time you want to type.)
I haven't had time to install it, but it's purchased.
Click to expand...
Click to collapse
I was just using google voice to text from several feet back. In fact it was hard to read the small print from that distance. I did not realized that keyboards have a larger range then headsets.
Testing Bluetooth Keyboard JP now. Force closes, so just switched to swift keyboard I downloaded from amazon app store for free. To get out swift keyboard and get a null keyboard, I hit the back key on the xoom keyboard, then the virtual swift keyboard no longer shows up.
@chisleu do you have a link or instruction to modify bluetooth keyboards so that keys can have their mappings corrected. Xoom has some correct and some wrong or disabled under CM7.
Couldn't get BT to work at all however powering down while the wifi is off, and turning the bluetooth on before the wifi made it works on the first try. Was streaming Slacker to my stereo in a matter of minutes. Wifi doesn't seem to interfere with the BT audio stream at all, audio sounded crisp and perfect. Range however was still limited to a foot or so.
Hoping there is a possible hardware mod that can hook up an antenna to the BT chip. I'd be in heaven if I had full BT functionality on this beast.
FYI, Although I don't have any RF experience I'm still an electrical engineer so if anyone can toss me a bone on the PCB layout or pinouts of the nook I might be able to try stuff to boost the range.
What is the feasibility of adding dial-up networking client support to CM7? Some folks are able to tether their NC to their phone using an ad hoc wifi network, and others have had success via a Bluetooth personal area network (PAN) using the "pand" utility. Unfortunately, I have a Blackberry phone, and it does not support the PAN profile. It does, however, support dial-up networking (DUN) over Bluetooth (confirmed with a Windows laptop).
According to https://sites.google.com/a/android.com/opensource/projects/bluetooth-faq, "dund" is the client utility that is needed to establish a dial-up connection from Android to another device. When I run this command on the NC, it says "dund: not found". I'm not a developer and don't know how much effort would be involved in adding this functionality to the build. Is it just a matter of including the binaries, or is there additional development work involved?
Thanks in advance..
Has anyone noticed the following ?
a) Turning on / off bluetooth affects the WiFi connection including sometimes disconnecting the WiFi (when BT is being turned off i.e.).
I use BT to connect with the gtab to my samsung and transfer files etc. When o go to disconnect, the wifi connection has also dissapeared.
b) As a side issue, the Market app kept force closing when launching it, when i changed to went to a different location and it connected up with the WiFi connection there. The Market app was active at first location before i left. Haven't had a chance to reproduce and check the exact scenarios yet.
Have stock Froyo (3389) with Enhancement 3.1.4b (Market app).
i suggest going to custom rom.
i had dropping wifi issues and those fc issues but it was due to a poorly made rom brillant corners and since theres no support i gave up on it
other froyo roms like beastly worked great. didnt drop conenctions
cahuja said:
Has anyone noticed the following ?
a) Turning on / off bluetooth affects the WiFi connection including sometimes disconnecting the WiFi (when BT is being turned off i.e.).
I use BT to connect with the gtab to my samsung and transfer files etc. When o go to disconnect, the wifi connection has also dissapeared.
b) As a side issue, the Market app kept force closing when launching it, when i changed to went to a different location and it connected up with the WiFi connection there. The Market app was active at first location before i left. Haven't had a chance to reproduce and check the exact scenarios yet.
Have stock Froyo (3389) with Enhancement 3.1.4b (Market app).
Click to expand...
Click to collapse
Just curious as to where you got stock 3389 from? It wasn't even released as an OTA update as far as I know. if you prefer stock, then 3588 or 4349 are the most used versions. Have you made any other mods yet? CWM, market fix, etc? If not, then using stock recovery, you can flash either of the stock roms. See Goodintentions "Gtablet for dummies" page for links to the images, and instructions on how to flash using stock recovery.
I, too, have the same problem. On my first mod TnT Harmony 1.2 and now with Caulkin's G-Tab 1.1 I have a problem with bluetooth causing interference with wifi. I am using the BlutO keyboard along with "Bluetooth Easy Connect" in order to get it to actually connect. However, on both mod's the effect is the same, as soon as I turn off the bluetooth my wifi stays connected. I really like Caulkin's G-Tab it is amazingly fast and would prefer to stay there but would move to another one if a different mod would solve this problem. Any suggestions?
Oops must have been typing the rdp port too many times that day. Sorry its 3588.
Sent from my SGH-T959 using XDA App
I didnt want to take a chance with any particular complete rom replacement, thats why used the 'enhancement' pack which basically provided the speedup with market and still the std tnt ui.
Followup, yesterday I had to rebuild the 'bricked' gtab which was suffered from fc's just as I started to give demos :-((
So mucho thanks to the viewsonic for dummies site for collecting all the info in such an easy to read format
I did code red procedure and did the bocksize change which I had not had to do first time. Noticed a speed up in the stock (quadrant - 1743) just by doing a wipe and change of blocksize. Then adding enhancement pak took it to 2400.
Happy now. Tab is going to the field in uk, and hopefully will live thru next 3 wks without incidence.
Problem with bluetooth and wifi still exists. Basically turning on bluetooth and connecting will stall the wifi - it looks like it is still connected but open the settings panel and it will update to show 'disconnected' then touching the button will turn off wifi, then touching it again starts it connecting again and then its fine. A pain when you are trying to hookup bluetooth gps and use maps app.
Sent from my SGH-T959 using XDA App
I think this is the proper place for this, but feel free to call me names if it's not.
I just bought a Focus, and was using the Sync system with my Thunderbolt with no issue. Then about a week ago, I switched over to using CM7, now I can't make an outgoing call. There's no volume in the car, and if I manually turn Bluetooth off on the phone, I can hear the person I'm calling, but they can't hear me.
The weird thing is that if I get an incoming call, I can answer it through the car, and everything works without problem. I also don't have any issues like this with other Bluetooth devices. I've tried deleting the connection between car and phone, and re-pairing them, but get the same result.
Anyone who could suggest something would be my hero!
only thing I can think of is that cm7/aosp roms use a different BT stack then sense based roms (stock or otherwise). I'm guessing this stack which is usually better, isn't doing something right. I would try a sense based rom and see if your problems resolve.
vodkaequalslove said:
I think this is the proper place for this, but feel free to call me names if it's not.
I just bought a Focus, and was using the Sync system with my Thunderbolt with no issue. Then about a week ago, I switched over to using CM7, now I can't make an outgoing call. There's no volume in the car, and if I manually turn Bluetooth off on the phone, I can hear the person I'm calling, but they can't hear me.
The weird thing is that if I get an incoming call, I can answer it through the car, and everything works without problem. I also don't have any issues like this with other Bluetooth devices. I've tried deleting the connection between car and phone, and re-pairing them, but get the same result.
Anyone who could suggest something would be my hero!
Click to expand...
Click to collapse
I'm using TheROM V4 (aosp) rom, and previously was using CM7. Have been able to sync with SYNC with no problems. I would try deleting the BT connection in your car first, then re-pair your phone. If that doesn't work, try downloading and flashing CM7 again. If that does not work, and you like AOSP ROMs, then try one of the other ones (OMGB, OMFGB, TheROM, or Thunderstick).
Sometimes my sync starts acting up in my 2009 focus. Only thing that remedies it is a master reset on your sync under system settings and then pair the device again.
Sent from my ADR6400L using Tapatalk
You also might want to check if your sync system has the latest updates from syncmyride dot com.
Sent from my ADR6400L using Tapatalk
The Ford is the problem. Get a Chevy will fix the problem. lmao
I rooted and have s-off but have an issue since. My bluetooth headset will no longer stay connected to the phone (constant connect/disconnect). I tried to do a fix permissions via recovery as well as wipe cache/dalvik cache which didnt help and caused all of my contact pictures (in the messaging app too) to no longer show. Any suggestions as to get my bluetooth working again?
This has been hit or miss as I have flashed about 5 different roms and sometimes the bluetooth is more sensitive. I just flashed the newest radio update and was hoping that would fix that problem.
Recoil737 said:
This has been hit or miss as I have flashed about 5 different roms and sometimes the bluetooth is more sensitive. I just flashed the newest radio update and was hoping that would fix that problem.
Click to expand...
Click to collapse
I flashed the new radios yesterday and it doesn't appear to correct the problem. This is frustrating as I just bought the EVO LTE (coming from OG EVO) along with a brand new earpiece and can't use the earpiece. I haven't flashed any ROMs yet, still running stock.
I'm running the 8/31 build of cmx and my Bluetooth audio disconnects occasionally and sometimes requires a reboot to connect. Also my phone calls rarely go to my Bluetooth.
Sent from my EVO using xda premium
Hiya,
So I managed to get my phone rooted and flashed a new ROM or two (PACMan and CM10 and 11) and in each one the bluetooth was essentially not there. I could toggle the switch, but no bluetooth would show up, and the actual bluetooth menu is empty. I've searched a bit and couldn't really find a definative statement on the issue. Is it just me? or did i miss some note stating the issue?
I'm on CM11 and have had no issues with Bluetooth.
Sent from my Nexus 7 using XDA Free mobile app
I haven't issues too
Interesting. So I just tried to run Tablet Talk and it said Bluetooth isn't supported by this device.
No BT issues here.
I updated to m9 today and Bluetooth would not connect then would not turn on when I tried to cycle it I wiped cache and dalvik cache rebooted and it connected fine. Might try that if it's still not working for you.
Sent from my Nexus 7 using XDA Free mobile app
wmuflyer said:
I updated to m9 today and Bluetooth would not connect then would not turn on when I tried to cycle it I wiped cache and dalvik cache rebooted and it connected fine. Might try that if it's still not working for you.
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for the reply. So i did a bit of experimenting. First I went back to stock. BT actually worked. Next reloaded CM11. Again BT was OK. The I restored my backup data. Suddenly BT was not OK. So I simply went back to a clean CM11 install and loaded my data bit by bit. I never actually figured out what was causing the issue - the issue being that something was telling the phone that it did not have bluetooth capabilities - but I imagine that it was so specific and unlikely that it isn't much of a concern.
That is interesting about the davlic cache. I did not try that.