yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] chisleu:
I have found it is strictly related to wifi activity. If I start a download it becomes very fruity. Turn off wifi and it's fine, but turn on wifi and while it's negotiating the connection it freaks the BT the F!@# out.

I go on break and vactation in ~3 weeks and if it's not addressed by then I'm going to spend a ****load of time figuring it out. I might not fix it, but by god I'm going to try. haha
[Nook Color Android Development] quinxy:
Ah, very interesting observation. I can see now that my experience may match that quite well, just a few minutes ago my typing suddenly froze and it lost a bunch of stuff in the keybuffer when Gmail was saving a draft. Other times it might be retrieving email in the background when I have trouble. I've seen this discussed a bit, the BT and wifi conflict. Any progress made? Or on BT range? I assume the range and BT-wifi conflict might somehow relate. What about a hack to temporarily severely limit the wifi speed while you're using BT keyboard? I wonder if that would fix it? I mean, email is constantly being checked in the background and presumably the problem only occurs when an item is retrieved, not merely when the server interaction is confirming no new mail... So if we could just limit the wifi speed while you're using the BT keyboard, maybe that would be a temporary workaround? Apologies if that's been proposed.

Q
[Nook Color Android Development] chisleu:
The range is a software issue (we think) and is way above my pay grade.

The bt/wifi issue may be a configuration and software issue. It might be easier to fix. Worth a try for me. I just don't have time until exams are over.
[Nook Color Android Development] khaytsus:
Antenna runs along the bottom and up the right side as you hold it portrait with the N key at the bottom.
[Nook Color Android Development] sark666:
I thought this was very good news about TI releasing the source to some of their chips one of which the Nook uses for bluetooth. However the thread has been closed. Anyone know why?

http://xdaforums.com/showthread.php?t=1036747
[Nook Color Android Development] chisleu:
Yeah, What the hell. I was looking forward to progress on that. Why is it close? Probably a mod thinking it was heading into the "maybe we can get the FM radio to work!!!!" crap.

Make a new thread IMO.
[Nook Color Android Development] dalingrin:
We already know about OpenLink. No worries.
[Nook Color Android Development] chisleu:
#1 coder award.
[Nook Color Android Development] bhojo1:
actually bluetooth does work without an antenna,

My acer aspire1 came without bluetooth so I bought a half height wifi bluetooth combo card and put it in the free slot. Now I did n't connect any of the antennas to the card but I am happily using my microsoft bluetooth mouse with the card .

SO looks like the traces are enough for limited bluetooth coverage...

i'm betting they can be pretty small for bluetooth, but not non-existant.

What I mean to say here is: If there wasn't an antenna of significant length, it wouldn't receive at all. The connection between an pin and chip die isn't going to pick up signal that's usable.

If you would like to prove me wrong though, open up a laptop, disconnect the wifi antenna cables (easily removed/connected) and see how well it works with 2 .5mm antennas ;)

...

To the developer working on this: Awesome work, and my hat is off to you for your progression and contributions to the device & associated work.[/QUOTE]

I second this , now that bluetooth is out in the wild hats off to you !!
[Nook Color Android Development] Arbelzapf:
How are evryone's experiences with beta 3.1?

I can't use my bt keyboard any more, nor can I pair my NC with my Wildfire

The keyboard does pair with the Nook, but it just does nothing. Logcat shows the device code and the pairing process, but it does not seem to pick up a keychar map like it used to
[Nook Color Android Development] chisleu:
havn't tried. charging my keyboard now to test.

It worked fine with my phone GPS tethering over BT
[Nook Color Android Development] chisleu:
Yeah, it is not just you. BT was known to have bugs in the .32 release and this must be one of them.

Good find.
[Nook Color Android Development] Arbelzapf:
Okay thanks for confirming :)

I just gave it another try myself right after rebooting -just to make sure. I even removed all BT devices and re-paired my keyboard.

Same outcome
[Nook Color Android Development] breebauer:
I'm on beta 3.1 with OC kernel:

I don't have a BT keyboard, but I can pair and connect to my car stereo

I think the range is still the same... a few inches
[Nook Color Android Development] sark666:
I mentioned this awhile back, a closed thread regarding releasing the source for various chips including one supposedly used in the Nook. It was mentioned back then the developers are aware of this.

So has anything come of this yet? I don't mean to sound like I'm complaining, but I was hoping bt support would have come along a little more by now. Has the range issues been solved at all? Is there any known headset/mic that works for voip?

I'm referring to this thread:

http://xdaforums.com/showthread.php?t=1036747
[Nook Color Android Development] verygreen:
Headset/mic not working have nothing to do with bt and everything with alsa/soudn implementation in android for Nook
[Nook Color Android Development] chisleu:
Old news. Developers know this stuff already.

I don't think sound input works? Even if it did, it would be extremely short range.

In a few weeks I hope to have enough time to dive into the bluetooth. Don't know that I could actually do anything, but I do know I might have time to try! :)
[Nook Color Android Development] Wipeout:
OK, now I feel a bit better that it's not just me (n94 in my case).
[Nook Color Android Development] dexx0008:
yep it isn't just you, my functioning bt keyboard stopped working after getting off 7.0.2 stable and getting on .32 kernel (currently n94)
[Nook Color Android Development] :
Oddly enough, my bluetooth keyboard works perfectly with the .32 kernel. It is actually much more reliable than it was on the .29 kernels. . .
[Nook Color Android Development] Arbelzapf:
I wish it would just work again :( Now that I can use my usb-mouse, I really need a keyboard to go with it, but I only have PS2-keyboards.

It really sucks that I spent so much money on a keyboard from a company I would not normally buy products from, only to see it collecting dust :(:(
[Nook Color Android Development] chisleu:
Worse yet, my bluetooth keyboard stopped working all together. It won't hold a charge and only works when plugged into USB. I guess now I could use the USB port to power it, but wtf...
[Nook Color Android Development] sark666:
Sigh, I swear I posted a reply but maybe I only hit preview.

So are you saying that lets say tomorrow all sound/alsa issues were resolved, then we'd have bt headsets/mic working without issue?

I'm under the impression that even if they were resolved, many devices still wouldn't work and even if they did, the range issue would still be apparent, or is this no longer the case?

And why is this only an issue with the nook regarding sound and android? I would have thought there would have been some type of abstraction layer for sound routing (recording and playback) and that once the hardware was recognized this wouldn't be an issue.
[Nook Color Android Development] verygreen:
Sort of. Some of my extra digging indicates there are some important glue missing in our libaudio/alsa combnation to make sco devices (headsets basically) work.

the range has nothing to do with audio. Even when the audio is fixed, the range issue will stay (I am not sure of the nature of the range issue? An antennae that is only optimized for wifi? (though the frequencies should be shared, but who knows)).

You can see that the range is pretty bad for non-audio devices too ;)

Well. For a2dp there is some extra glue in audioflinger, but only for a2dp.

For sco headsets the are controlled from libaudio and all phones with android supported by CM7 seem to support their own libaudio that deals with the proper routing there.

This is combined with a fact that bt_sco audio is no longer a proper kernel driver, but rather a userspace alsa plugin.

I have both sco and a2dp devices. A2dp device does work right now with 0 problems.

Then there is a matter of generic bugs, like the one I found yesterday working on usb microphone support (http://review.cyanogenmod.com/#change,5985) - a small typo means omap3alsa module would incorrectly match request for sound input as sound output request. You might imagine what that leads to once you try to actually record something later on ;)
[Nook Color Android Development] paleh0rse:
Can someone please describe for me the exact steps used to pair a wiimote in cm7 n96? I cant seem to get it to show up... :(
[Nook Color Android Development] chisleu:
The range is only bad for transmitting. I used to be able to use my keyboard from across the room.
[Nook Color Android Development] verygreen:
My keyboard only reliably works from a couple of feet. Any further apart and it gets really unhappy.
[Nook Color Android Development] paleh0rse:
Anyone? Please? I'd really like to play some snes and n64oid tonight! lol
[Nook Color Android Development] Therev29:
Download a wiimote app from the market. Install. Go into settings-language keyboards. Select the Wiimote. Go into the wiimote app. it should have the instructions there. press 1 and 2 on the wiimote to pair and select pair in the wiimote app. After it connects go into your emulator and set the hardware keys to your wiimote. Enjoy!
[Nook Color Android Development] paleh0rse:
You're the man (or woman?)... thank you!

It's time to play some GoldenEye.. Woohoo!! :)
[Nook Color Android Development] rhester72:
Good luck with that. Goldeneye is glacial on N64oid - it's really only useful for Super Mario and Mario Kart. :/

Rodney
[Nook Color Android Development] paleh0rse:
Hmmm... damn, that's what I was afraid of. Is that true even at 1.3ghz?
[Nook Color Android Development] Divine_Madcat:
Pretty much. The problem isn't so much clock speed, but the emulator itself. It was just no complete, and had performance issues with almost every ROM out there, regardless of hardware. Cannot hurt to try of course, but don't get hopes up; thats all. :)
[Nook Color Android Development] DigitalMD:
Just curious, any ongoing driver / kernel work on extending the BT range or supporting headset / handsfree?
[Nook Color Android Development] DigitalMD:
Even with short range I would love to hve SCO audio for a mic input (headset)
[Nook Color Android Development] norkoastal:
7" nav screen with music output and and BT mouse controls for $250 = Magic!!!
[Nook Color Android Development] KryptoNyte39:
Sweet mother, I'm with ya. Kind of wish I had something to add to the team's efforts ...
[Nook Color Android Development] f4phantomii:
My first thought was that I could try to connect my older Garmin GPS BT receiver module and see if it would drive the maps/nav apps.

The Garmin module is nice because it can stay plugged into my wife's vehicle and then if she wanted to take it with her to walk around town or something you can just unplug the module and stick it in a pocket.

The phone idea is interesting, although I suspect I'd probably just use my phone!
[Nook Color Android Development] KryptoNyte39:
I suppose we would need some kind of stand-alone Android navigation application, with on-board maps ...
[Nook Color Android Development] madfatter:
or you just wi fi tether 3g from your phone. I have done this on all my Holiday trips the last few weeks and I have to say it works great. Not sure if that would work while using phone as GPS though
[Nook Color Android Development] KitF:
I'm pretty sure Pandora and the stock music/video player could use A2DP headphones, but other than that you're probably right.
[Nook Color Android Development] lifeisfun:
There is many available, I use Copilot Live on my Desire
[Nook Color Android Development] madfatter:
maybe, but maybe not. the pandora that is included is different than the pandora on the marketplace. It might be a stripped down version of it.
[Nook Color Android Development] KryptoNyte39:
What others are available? Maybe something with some fairly decent reviews?
[Nook Color Android Development] fwdixon:
This is good news indeed. I was waiting on the Salting results to make the purchase decision, as bluetooth is the only thing "missing" that I need in a tablet. Now that I know it is there, I'm gonna be making a trip to B&N.
[Nook Color Android Development] Bimboy:
http://www.alk.eu.com/copilot/android/

http://www.navigon.com/portal/us/produkte/navigationssoftware/mobile-navigator-android.html

Both Co-Pilot Live and Navigon are in the marketplace.
[Nook Color Android Development] gtriever:
Asus EeePC with touchscreen mod, 10.2" nav screen, music thru the MP3 input to my SUV stereo system, mounted in my home-built Ford Explorer stand = Bigger Magic!!! Plus, it runs DeLorme's Street Atlas and Topo USA, which are killer NAV apps! I'm just sayin'... :D

But, I'd like to see what the NOOK could do with CoPilot Live. Sounds interesting.
[Nook Color Android Development] diomark:
Awesome:-) this addresses one of my main issues with the nook :-) (the other issues being low sound volume, slow browser which will hopefully be fixed with froyo, and the screen being too responsive to taps...)
[Nook Color Android Development] jameswei:
congrats occip you've made it onto Engadget asmist all this CES coverage as well.

engadget.com/2011/01/04/nook-color-bluetooth-chip-shows-signs-of-life-if-youve-alrea/
[Nook Color Android Development] dethduck:
Wait...

it's an eReader.

Why the hell does it even have a bluetooth radio?
[Nook Color Android Development] ZeroSX:
Because most android devices are built from generic parts and overlayed with custom software. The OMAP SOC has an integrated BT radio.
[Nook Color Android Development] HotShotAzn:
1) B&N billed it as more than an ereader (look at the "extras")

2) Its on the chip, B&N deactivated it. Most likely, B&N got a good deal on the chip so they went with it.
[Nook Color Android Development] gedster314:
Probably because a wifi chip that only does wifi was too expensive. Its the whole economy of scale thing. Multifinction chips are in more demand so there is more production and therefor cheaper.
[Nook Color Android Development] starkruzr:
Marketing does not make essence.

What it IS is a 7" Android tablet. The fact that it is marketed as an ereader doesn't change the facts of what it is.
[Nook Color Android Development] dethduck:
Ah, ok, all those reasons make sense.

Thanks.
[Nook Color Android Development] techboydino:
Not that my post is helping with the clutter but......

The OP has 1 single post which is a fantastic one, the other 5 pages worth is all BS about what programs to use it with. Remember the Thanks button and keep it to the development.

For BT fantasies I say open something up in general. But then again I'm just some idiot who decided to chime in and make yet another post that has nothing to do with BT developement. Either way, thanks OP. :D
[Nook Color Android Development] italiano1964:
Congrats occip! You ended up on Engadget!

http://www.engadget.com/2011/01/04/nook-color-bluetooth-chip-shows-signs-of-life-if-youve-alrea/
[Nook Color Android Development] yerand:
didnt you just ask the exact same thing on engadget? 0_o
[Nook Color Android Development] occip:
not yet fully working

Thanks, Yes that's great.

If you think about buying NC for the bluetooth, please wait for full working bluetooth.

I cannot guarantee a success.

For BT audio, WL1271 can ouput directly in PCM to sound chip . I don't know if this part is well connected, otherwise over HCI it could be OK...

I continue to dig ...

Occip
[Nook Color Android Development] ThrowingKs:
Have you read what dahonda has mentioned in this thread?:

http://xdaforums.com/showthread.php?p=10331268

Particularly the posts around 35. Maybe, you guys can help each other?
[Nook Color Android Development] 30secs:
FORGET Skype. Gmail Phone is WHERE ITS AT!
[Nook Color Android Development] aaltieri:
Wait...is there actually anyone on any of these forums that use the products how they were actually INTENDED or marketed to be used!?!

I have to admit I'm taking the news that there's definitely BT love to be found in the nook a little hard. I just picked up the Viewsonic Gtab. Now I'm torn.

--mop
[Nook Color Android Development] jtbnet:
Well are you in for another nice surprise when you see how much better than delivered stock that tablet is once you load clockwork 0.8 and the latest Vegan Rom B5.1 :)
[Nook Color Android Development] nrune:
Not me bought mine to hack and man has it paid off. Love it!
[Nook Color Android Development] aaltieri:
I gave myself two hours with the stock rom. Not by choice, of course. I was trying to start the browser.

I'm vegan (wow...never thought I'd say THAT!) and loving it! My concern is that I think this tab might be a tad large for the intended purpose. Well...that and the screen is rubbish. But it is a fantastic tablet.

So I think I'll have to break down and get some nookie while the gettin' is good!

--mop
[Nook Color Android Development] mburris:
Eeepc touch mod is nice, but it's no capacitive tablet, thats for sure.
[Nook Color Android Development] occip:
some BT news

Yes, I have read this. It will be helpful.

Now few news (good and bad)

I managed to send a file from my NC to my phone using BT !

The BT range seems to be poor ( 2 foots), I hope this a configuration problem and not hardware one.

The uart link runs at 115200 bauds , It's low, higher baud rates don't work well , I'm suspecting buggy uart handling (for omap). Perhaps we need to backport omap serial driver from recent kernel.

stay tuned

Occip
[Nook Color Android Development] spikey911:
2 feet better than no feet..

I wonder if its from lack of antenna.
[Nook Color Android Development] sp1kez:
Check out my 10" eee tablet mod

http://img600.imageshack.us/img600/9075/eee2.jpg
[Nook Color Android Development] ThrowingKs:
Amazing! This needs to be front paged. Way to go.
[Nook Color Android Development] kitzuki:
this is very exciting news
[Nook Color Android Development] cutterjohn:
clockwork is your friend, and it should be the very first thing that you add whenever and wherever possible, esp. if you're going to be hacking... (I've got both gTab & NC ATM...)

Nice find wrt BT. I wonder if the FM tuner works as well and is hooked up to audio output somewhere...

Vegan: Just make sure that you're munching on a nicely rare filet while installing it... I use TnT lite myself

Range: likely the lack of an antenna, but seriously how far away are the devices that you'd be using with it going to be from the NC?
[Nook Color Android Development] Divine_Madcat:
Not sure why people keep saying this - it is documents on TI's site that they use a shared antenna (since both radios are 2.4Ghz, though it does raise interference issues). IF there was no antenna, there would be no transfer, period.
[Nook Color Android Development] cutterjohn:
Actually even w/o an antenna it would work to some extent w/a VERY limited range... also there are some funny occurences that can happen where unintended parts can act as unintentional antennas as well, although that usually borks up electronic functionality....
[Nook Color Android Development] spiicytuna:
Great news! I am watching this thread as of now...

.
[Nook Color Android Development] RoboRay:
Having the antenna shared doesn't guarantee that the BT portion of the chip is connected to the antenna. It probably is, since the BT portion of the chip was apparantly connected to everything else it uses, however.

And there absolutely could be short-range transfer with the antenna disconnected. The "antenna" in that case would simply be the unterminated end of the wire or the pin on the chip that should have been connected to the real antenna. Almost anything conductive can perform as a poor antenna. Since such an accidental antenna would not have the optimal physical characteristics for the wavelength of the radiated signal, the effective range would likely be extremely low but still yield useable results.
[Nook Color Android Development] spikey911:
Also if the pin for antenna is accessible, there is no reason an antenna couldn't be soldered on if it is in fact missing, but no point in getting into that until the determination can be made.
[Nook Color Android Development] fventura03:
This is amazing progress!
[Nook Color Android Development] mastapsi:
The chip is BGA so all the pads are inaccessible. We have to play with whatever B&N gave us.
[Nook Color Android Development] cybertimber2007:
Not trying to be a know it all here, but I do have some knowledge on this.

I took a year long course on Wireless Technologies, focusing on WiFi, WiMAX, and Bluetooth (plus some Zigbee and such). The antenna would need to be of a length proportional to the signal amplitude (ideally). Typically 1/2, 1/4, 1/8th, nothing noted smaller ratios. They aren't 1/1 because transmissions from AM radio stations would require 1,875ft (566m) antennas. 900Mhz cell phones would need 13 inch antennas (Wireless# Guide to Wireless Communications, 2nd edition, Pg 134, ISBN-13 978-1-4188-3699-3. Can probably find on Google Books.) Being that we can put antenna in bluetooth headsets, i'm betting they can be pretty small for bluetooth, but not non-existant.

What I mean to say here is: If there wasn't an antenna of significant length, it wouldn't receive at all. The connection between an pin and chip die isn't going to pick up signal that's usable.

If you would like to prove me wrong though, open up a laptop, disconnect the wifi antenna cables (easily removed/connected) and see how well it works with 2 .5mm antennas ;)

Secondly, the book does cover the use of the same antenna for both Wifi and Bluetooth. Two reasons for it: 1) Cost. Cheaper to use one antenna for two purposes, otherwise you'd have to have 2 antenna (copper = $), two band-passes for 2.4ghz range, seperate connections, board trace space, etc etc etc. 2) Interference. If you have two 'large' antennas in close proximity, they would interfere with each other. Add in that both work in the 2.4 GHz range, and you can quickly spell chaos.

What I mean to say here is: It's already implemented in hundreds of products. Don't debate that that can't be the possibility here when that's how TI says it's to be used. Plus, we shouldn't be judging something like this yet because it isn't performing like a normal bluetooth reciever. The Salting will show exactly what we are working with, and further investigation and trial/error with bluetooth will give more insight into the capabilities we have with the bluetooth chip. A week ago some had given up hope on it. One little post changed that ;) Three days ago, we didn't think anything could transfer. Now that's changed too.

To the developer working on this: Awesome work, and my hat is off to you for your progression and contributions to the device & associated work.
[Nook Color Android Development] RoboRay:
Uh, yes, it is potentially true. You yourself said "(ideally)." A non-ideal antenna can be surprisingly functional. In 20 years of working with (often prototype) electronic signals collection equipment, I've personally seen usable RF reception in the target frequency range picked up by incomplete development/testing hardware that was completely missing the entire antenna system. Was the signal strength good? No, it was horrible, but that doesn't mean it didn't happen at all.

And ideal antenna length is proportional to signal amplitude? I'm sure you meant wavelength.

Signals in the GHz range only require tiny antennas due to their relative high frequency (and therefore, short wavelength). The closer to 1:1 the better, of course, but so long as you're reasonably close to one of the harmonics it can work, even if the actual ratio is quite high. You don't need much for a borderline-SHF antenna.

So, yes, it is theoretically possible, however unlikely. I'll even give you "extremely unlikely." I'm pretty confident that the NC's BT is is connected to the antenna, anyway, since apparently everything else for the BT function is there.