yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] Dj-Gutz:
No.

The problem with the GPS is probably the port number

our nook assign it to ttyUSB0 while the apps are supposed to look for ttyUSB9

Only one other device has documented USB GPS working on android and its the ZT-180

I Managed to find what I think is the solution while comparing sources between the zt-180 and the nook

I actually PMed dalingrin about it a couple of weeks ago but never got an answer ( I guess he is focusing on his TP )

I'm on vacation so I can't give you the exact code but if you are a dev I can ask dalingrin to publish my PM so you can finish the job

I also need this to work
[Nook Color Android Development] jameshmiller:
No, I'm not a Dev:( I just haven't seen any updates on this, then saw the USBTTY comment on the latest nightly (206) and got excited. Thank you for the update. Maybe someone else could chime in? I know Dalingrin has been busy with the TP.

Enjoy your vacation!
[Nook Color Android Development] DigitalMD:
The easiest solution is to use the GPS tether app and tether GPS to your phone, if that will work for you.
[Nook Color Android Development] Dj-Gutz:
obviously I know my options, but thanks

I'm installing the nook in my car and I have a usb-gps already that I wish to use

also, I'm not the only one who drives the car so I need constant gps
[Nook Color Android Development] 12paq:
@Moshe5368 PM sent.
[Nook Color Android Development] shoaib17:
Has anyone tried hosting Ev-do usb dongle using nook color? Because I am planning to buy a microUSB to USB Female adapter just for the ev-do dongle. So that I can have internet on the go. There won't be any issue right? as nook color is capable of hosting usb devices using this method.
[Nook Color Android Development] therkr:
Will webcams be ever supported in the 7.1? Or are they even supported in the latest nighties?

Is yes, which ones.

Thanks.
[Nook Color Android Development] ganovim:
Kol Ha Kavod

What is missing, is a usb mic driver that works on cm7.1

I have tried usb audio out, and that works fine (with a usb audiocard dongle), but

audio in (recording and skype) does not work.
[Nook Color Android Development] Moshe5368:
skype may never be a possibility on the nook as the drivers are not available. microphone input has always been an issue and spotty at best.
[Nook Color Android Development] j8048188:
alsa.omap3.so mirror?

Does anyone have a copy of VeryGreen's alsa.omap3.so that they could upload/send? Is this needed any more in CM7.2, or does the build already have the correct one included?

Thanks!
[Nook Color Android Development] Pinesal:
Wow, this is really cool.

But how does a mouse work on the Nook? Android isn't programmed with a mouse in mind is it? Do you have a mouse cursor when you plug in a mouse? Does the scroll wheel work?
[Nook Color Android Development] verygreen:
Like I said in the first post, the generic audio is enabled.

Whether it will work with alsa we ship I don't know, though I guess it's worth a try.

I wonder if my webcam with microphone will draw more than 100mA or not. Need to try it, I guess.
[Nook Color Android Development] MadMikeSS:
Nice work, I'd like to see working gps device attached to the nook... That would be cool.
[Nook Color Android Development] Divine_Madcat:
To be fair, you could already do that for a long while with bluetooth. This is great for storage, controllers, and webcams though, and i cannot wait to get my adapter Friday...
[Nook Color Android Development] ADude:
When BT was enabled, people were talking about audio playback, but not about input, and earlier on, there was some doubt as to whether the dormant NC audio input could be activated or not - hence my question.

PS All this is very cool and appreciated.
[Nook Color Android Development] :
It looks and acts just like it does in *Nix. cursor, clicking, the whole 9 yards.
[Nook Color Android Development] deadbot1:
So my question is this... I want to make a "backpack" for my nook. It'll have a camera, hub, and battery with voltage regulation for USB power. Will I be courting disaster with the battery if I connect it to the nook(for simultaneous charging)?
[Nook Color Android Development] BitingChaos:
Are you serious??

The first Android device ever (HTC Dream / G1) had a mouse/trackball built-in. A mouse cursor has been a part of Android since 1.x!
[Nook Color Android Development] verygreen:
If you plan to power the usb from the battery, it's possible to enable a different operating mode (not part of this kernel) where nook does not try to supply vbus but charges from it instead. This seems to be a popular request, so the next version will have such ability/setting.

When nook tries to supply vbus and there is external vbus power source too - I do not knwo what will happen. I had a chat with EE today that assured me if the HW designers were worth anything, nothing bad will happen as long as the nook battery charger stays disabled (and it is disabled when you enable host mode). If the battery would be enabled then there is a potential short circuit issue looming.

Anyway I am a bit too risk averse at the moment to tr host mode+nook vbus with additional external vbus power source. ;)
[Nook Color Android Development] Taosaur:
If anyone wants to take a stab at getting TV tuner sticks working, I found this active project for the Archos Gen8 tablets: http://xdaforums.com/showthread.php?t=871391

I'm pretty sure he's working with Android 2.2 and .30 linux kernel, but he already has a basic apk to work with TV tuners, and maybe some of the other work will translate.

I'll happily be a test monkey once I get my hands on an adapter (thought I had one, but it's male/male and not standard mini-USB :P ). I have a Pinnacle HDTV Pro Stick ATSC tuner.
[Nook Color Android Development] rigy73:
Hey green can you tell me what i would have to do for high rate charging form a normal usb cable i have the original charger,

and can shorting the data pins with the live pin also do the trick, and would it be risky to try.
[Nook Color Android Development] :
So is there a reason the NC cannot run a Logitech illuminated keyboard or my wireless mouse on it's own, but when I plug a non-powered hub into the NC, it can use both?

EDIT: Also just hooked in LifeCam HD (6000? Whatever the notebook edition is) and didn't get anything in reelportal or yahoo. Will try the hacked Oovoo sometime...

An interesting thing I found. I cannot get anything fancy to work by itself (logitech illuminated keyboard, wireless mouse, webcam), but if I use a hub without external power (using external power seemed to make everything act really weird on the NC [phantom touches, etc...thought I fried it at first!]), I can plug in all sorts of goodies.

As far as the app goes, I think integrating into Dal's volume app (as he recommended) would be best. Great work on this! Maybe it's time I sell my netbook....if I could only get a usable matlab port (mathmatiz and addi aren't there yet...need good m file support).
[Nook Color Android Development] bassrebel:
There you are :D

Good to see you roaming around here too
[Nook Color Android Development] verygreen:
I guess the reason is - the hub hides the power profile (or makes it appear as irrelevant).

The CM7 for nook is compiled without camera support so you need to recompile with camera support first for any camera to work I would imagine.
[Nook Color Android Development] hololight:
Do not short vbus onto the data line.... I can see no good coming from that.

Three ways they could be signalling high current charger:

1. Short d+ and d-

2. Specific resistor on I'd pin

3. Using one of the 12 deeper pins on the connector (if anyone can confirm this is a mcpc connector let me know)

The source should show which of the 3 but I never looked.
[Nook Color Android Development] verygreen:
I read the charger datasheet again: http://datasheets.maxim-ic.com/en/ds/MAX8903A-MAX8903Y.pdf

And now that I look at it, it appears that the 2A power must be supplied via additional pin.

I can produce a patch that would enable 2A charging, but I am not sure what would happen if DC is not connected and only VBUS is connected.

I can produce a patch to this effect that would have toggable 2A/0.5A power draw and you can see what happens.

I don't have much time right now, though, the some urgent work (the kind that pays the bills) needs to be done. So I can make you a quick kernel patch and you can pick up the rest or we can wait until weekend where I will have a bit more time hopefully.
[Nook Color Android Development] chemical1der:
oh and about a month ago, around nightly 87 or 88 i think, there was a change submitted to enable mouse pointer support for bluetooth devices:

http://cm-nightlies.appspot.com/?device=encore

i occasionally pair a BT mouse with my Nook. now that there's USB Port support i'll definitely switch since I had time-out issues with the BT mouse.
[Nook Color Android Development] joenathane:
If you had a donate button maybe we could help pay some of those bills :p

Seriously, I wish there was some way we could really show our Nook devs some appreciation...
[Nook Color Android Development] mrmark93:
Through my own experimentation (see the 'Car Charger' thread on the Accessories subforum) I found that the NC needs to see shorted data pins to allow high-rate charging. iPad 2A chargers use the resistance across data pins method--this does not work for NC (it charges at the normal, slower rate). You do need to use the OEM Barnes & Noble USB-to-Micro USB charge cable as well to achieve the high-rate charge (cable has extra pins for current flow to prevent damage to the smallish-standard micro-USB connector pins).
[Nook Color Android Development] hololight:
Okay, so i read through the datasheet and looked at the source again:

A. data lines need shorted

B. max8903 needs signaled that it should charge in dc mode.

could be signaled from software (in theory at least, I can't find provisions for this in the datasheet), rather easily.

could fry your standard charger that one time you forget to toggle it out of high current mode (best case).

that is assuming that the dc input is wired to the usb vbus input (allowed by design, but no guaranty). the dc input could be one of the other 12 pins in the connector on the b&n cable (wired together in there), or one of those 12 is just the DC signal line.

Chris
[Nook Color Android Development] deadbot1:
Ok...thanks for the answer..very informative. I guess what I was thinking was a pass thru port....into backpack...out to nook...will need that vbus free version...thank you for all your hard work....if I made one of these with resistor on the ID pin..could we sense that and set the correct mode?
[Nook Color Android Development] verygreen:
We can try.

It would not be able to turn on vbus automatically on unpatched kernel anyway, since the driver lacks this ability, but sensing should be easy to add.
[Nook Color Android Development] chisleu:
USB GPS devices may not work because of the 100ma current limit. suck.

Buy.com - UniTraQ UD-731 USB 2.0 44-Channel GPS Receiver (Black)

I'm sure camera's are higher. Hopefully we can get camera support added in.
[Nook Color Android Development] TDO:
A normal camera has it's own power supply and transfers only data via Usb.

Only very cheap cameras use Usb for charging.
[Nook Color Android Development] Divine_Madcat:
MOst of the camera talk is about webcams, not actual cameras.
[Nook Color Android Development] rigy73:
sure you can make the patch. I'll try it out and see what happens although is there a way to lower the current to 1A i don't really want to damage my nook since i have no method to get it replaced.

I think i understand what you are saying, i took a quick look into the driver for max8903 and i got the different types of chargers that B&N has included.

If we do not want to use software to change the mode then we could just change the settings in the kernel for just a D+/D- shorted cable to do the charging and leave non shorted cable for everything else at normal 500mA

According to source there are

/*

5 types of charger:

I. DC charger: DC-CHG only, we charge via DC input limit 2A ( development use ONLY)

II. BN charger: VBUS/DC signal,D+/D- shorted, we charge via DC input,limit 2A

III. USB charger: VBUS/DC signal,D+/D- not shorted,charge via VBUS,limit 500mA

IV. USB charger: VBUS only,D+/D- not shorted,charge via VBUS,limit 500mA

V. USB charger: VBUS only,D+/D- shorted,charge via VBUS,limit 500mA

*/

There are a lot of things i could make out of this, but i don't really know what effect would changing the limit to 2A on usb charger have on the nook. And can anyone tell me what exactly is dc charger here.
[Nook Color Android Development] chisleu:
absolutely. I mean camera input support in CM7-encore so we can use them for something.

I just realized I could plug my digital camera in and copy files to the nook directly. EPIC. I need to buy an adapter now.
[Nook Color Android Development] martian21:
My guess is charging from a DC (Direct Current) power source like a car cigarette lighter adapter or something. is. 12V DC input as opposed to 110 AC (wall outlet)
[Nook Color Android Development] racks11479:
Well now that we have USB host working, think it would be possible to connect a bluetooth dongle to the Nook so we can use bluetooth devices with better range?
[Nook Color Android Development] verygreen:
DC charger is the DC pin in the charger pdf.

If you can just wait until tomorow, I'll put in a patch and some more explanations in a separate topic and no hw mods to the cable would be needed.

I had some discussions with pokey9000 who referenced someones teardown that found that the DC pin is shorted to vbus pin so we can draw right from there.

Also he found that common microUSB plugs are rated for 1.8A.

His earlier research shows that NC hardly draws this much anyway so should be safe to use: http://xdaforums.com/showpost.php?p=9410625&postcount=243
[Nook Color Android Development] verygreen:
Should be possible, but the kernel I made does not have usb bt support.

Another obstacle is Android has hardwired bt interface location. So you need to change it to another interface and recompile the entire thing.
[Nook Color Android Development] jamima69:
for what it's worth, flashing this kernel gets me a blackscreen on rebooting. (coming from phiremod 6.3)

ah well :/
[Nook Color Android Development] Divine_Madcat:
Because this kernel is not meant for the outdated Phiremod builds. This is a .32 kernel, where as the build you are using is made for .29 kernels. And, at the risk of being rude, this fact is plainly stated in the OPs post:
[Nook Color Android Development] waiteck:
is there a possibility that we can use our 3G dongles as well?

for archos tab, there is a workaround with their scripts and configuration which works at

http://xdaforums.com/showthread.php?t=940470
[Nook Color Android Development] skwalas:
Out of curiosity, would this USB functionality allow movies to be played directly off a flash drive?

And I know this is WIP, but will the final implementation include automatic mounting of storage? Or do I only have to create a mountpoint once and then its good for all flash drives?
[Nook Color Android Development] verygreen:
I see no reason why not.

This is more in the realm of Android. I am not sure gingerbread has a concept of usb storage, but I have not looked much into it.

On second thought, it should be possible to tell vold about usb storage, like if you always expect it to be at /dev/block/sda, you need to add a correponding line there (and create a mountpoint beforehand of course).
[Nook Color Android Development] Arbelzapf:
Okay second try with the xbox 360 controller -this time with a powered hub.

<6>[ 397.755920] usb 1-1.2: New USB device found, idVendor=045e, idProduct=028e
<6>[ 397.763427] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
<6>[ 397.771270] usb 1-1.2: Product: Controller
<6>[ 397.775848] usb 1-1.2: Manufacturer: Microsoft Inc.
<6>[ 397.781127] usb 1-1.2: SerialNumber: 10E7F90
<7>[ 397.786437] usb 1-1.2: uevent
<7>[ 397.792053] usb 1-1.2: usb_probe_device
<6>[ 397.796417] usb 1-1.2: configuration #1 chosen from 1 choice
<7>[ 397.802978] usb 1-1.2: adding 1-1.2:1.0 (config #1, interface 0)
<7>[ 397.809631] usb 1-1.2:1.0: uevent
<7>[ 397.815032] usbserial_generic 1-1.2:1.0: usb_probe_interface
<7>[ 397.821258] usbserial_generic 1-1.2:1.0: usb_probe_interface - got id
<7>[ 397.828613] usb 1-1.2: adding 1-1.2:1.1 (config #1, interface 1)
<7>[ 397.835266] usb 1-1.2:1.1: uevent
<7>[ 397.840667] usbserial_generic 1-1.2:1.1: usb_probe_interface
<7>[ 397.847015] usbserial_generic 1-1.2:1.1: usb_probe_interface - got id
<7>[ 397.854400] usb 1-1.2: adding 1-1.2:1.2 (config #1, interface 2)
<7>[ 397.861022] usb 1-1.2:1.2: uevent
<7>[ 397.867004] usbserial_generic 1-1.2:1.2: usb_probe_interface
<7>[ 397.873413] usbserial_generic 1-1.2:1.2: usb_probe_interface - got id
<7>[ 397.880554] usb 1-1.2: adding 1-1.2:1.3 (config #1, interface 3)
<7>[ 397.891143] usb 1-1.2:1.3: uevent
<7>[ 397.896881] usbserial_generic 1-1.2:1.3: usb_probe_interface
<7>[ 397.903228] usbserial_generic 1-1.2:1.3: usb_probe_interface - got id
<7>[ 397.910278] drivers/usb/core/inode.c: creating file '004'
<7>[ 397.916534] hub 1-1:1.0: state 7 ports 4 chg 0000 evt 0004

Looks better than last time, but the controller still does nothing at all (except helplessly blinking). But maybe that is the expected outcome at this moment?

Is there anything I can do to make it work? I tried assigning hardware buttons in FPse, but it didn't respond. Do apps need to support the controller as well?
[Nook Color Android Development] FRSP:
I'm not really seeing anything in your dmesg that I would (without knowledge of this peripheral) expect to be able to talk to it, such as messages from the xpad kernel module. The assignment to generic serial is a bit odd, though it could be that is how it is supposed to work.

I think a really productive step would be to compare the dmesg that results from plugging the device into a desktop linux, and also use lsmod (maybe as a before and after diff?) to see what drivers are loaded.

As a guess, support for the controller wasn't built in this kernel. But there also appears to be a libusb-based userspace driver out there on the net, maybe you could try that.
[Nook Color Android Development] seth.i.simmons:
You are using the wired (not wireless with plug'n'play cord) to try this right?? Just checking, since only the wired can be used without a wireless adapter.
[Nook Color Android Development] Arbelzapf:
Yes, it's the regular wired controller.

Is this the userspace driver FRSP talked about?

http://pingus.seul.org/~grumbel/xboxdrv/
[Nook Color Android Development] Decad3nce:
Thread cleaned. Keep it cute and cuddly people.
[Nook Color Android Development] verygreen:
By popular request:

I updated the kernel and the app with a new feature - Allow to force "External" vbus source.

What it does is opens the battery charger gate instead of driving vbus from TWL chip. In this state it is safe to connect nook to external power sources.

Additionally if you enable host mode when an external power source is detected, this is the default mode now (just in case). Attempt to switch from this mode to twl vbus mode while the external power is still connected is also blocked.

My testing shows that if you have very full battery, it might even drive vbus at sufficient voltage all by itself without any external power source.

Additional testing shows that switching power source in-app in flight when usb host is operated seems to mostly (but not always) work in the external->internal direction, but not the other way around.

If you switched the source and your device stopped working, it seem just unplugging and replugging is not enough and you need to disable and then enable the host mode again.
[Nook Color Android Development] Backwardsblade:
Man I am just counting the hours until my adapter comes. A quick question though, is .2 of the overclocked variety? Thanks so much for your continued development!
[Nook Color Android Development] verygreen:
It's a bit overclocked, but not overvolted, so only goes to 925 Mhz I think. Whatever the nonOC dalingrin's kernel goes up to.
[Nook Color Android Development] newellj79:
I just discovered this thread and quickly read all 11 pages, then ordered a adapter for $3.20. I'm very excited about the possibilities. I know this is in very early testing so its probably to early to ask that this functionality be implemented into dalingrins oc kernel. I can't wait to start testing and want to say thanks for your hard work.
[Nook Color Android Development] verygreen:
I just got USB camera working (to some degree. preview window shows stuff).

Only for uvc cameras supported by the kernel.

Most of the work was done by CoreDruids by adding support for v4l cameras to Froyo. I merely ported their work to current CM7 sources. (links to follow once I submit changes to the repo. I expect this to be interesting to a lot of people as lately there were released plenty of tablets without cameras).

My camera is MS Lifecam HD and seems to be too power-hungry for Nook to drive, so I used the just released ability to have externally driven vbus and borrowed the power from my desktop. Keep this in mind if you try with your camera and it does not work at first. (without it if I use the camera + keyboard on just nook power, stuff dies on init. If I use just the camera (over unpowered usb hub in both cases to hide power-hungry profile from the nook) it inits fine, but dies due to lack of power once real video stream is attempted (protocol error visible in logcat from v4l module)).

Edit: So here is a special nightly build with webcam support. Try Camera app, that one certainly works. http://nook.handhelds.ru/usbhost/update-cm-7.1.0-RC0-encore-KANG-signed.zip This nightly already includes usbhost enabled kernel, but you still need to install the usbhost switchign app separately if you don't have it.

Source changes for those interested. Generic libcamera stuff: http://review.cyanogenmod.com/5928 and Nook specific parts: http://review.cyanogenmod.com/5929
[Nook Color Android Development] miketunes:
Confused a bit on the "external" vbus source. Would I somehow be able to charge the nook and plug in a device in at the same time? I'm trying to figure out the best way to mount a 100+gb on my nook in my car.

Option A - I'm testing a wifi router with USB ports, seems to be having problems with hard drive when the router shuts off though.

Option B - microsd to SD adapter with 128GB sdxc card (I don't think nook supports over 32GB though)

Option C - this app, with a hub or something to hook power and hard drive up at same time?
[Nook Color Android Development] verygreen:
Yes. You basically need a Y-usb cable the ends with data lines plug into nook and the device you need to be talking to.

The one with just vbus lines goes into a 5v power source like a special battery or a laptop or a PC (I use a PC).

well, must be an implementation problem on the router side.

Nook supports arbitrary sized devices. The limitation is in the microsd controller on the nook. If you connect a usb card reader via USB and the reader supports such sizes, it will work.

This should work too.

Note that there is no robust ntfs support for Android that I am aware of that is your filesystem of choice.
[Nook Color Android Development] miketunes:
Would a cable like this work: http://cgi.ebay.com/USB-Y-CABLE-MICRO-USB-/230630392106?pt=LH_DefaultDomain_0&hash=item35b2a4812a

I'd plug the micro usb side in the nook, one regular into my usb hard drive, the other regular into the nook color car charger?

Also any ideas of any compatibility issues with sleep mode?
[Nook Color Android Development] mrmark93:
Mike-your link is to this page :D