yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] :
So I got it to work but I had to do the following steps manually after reboot:

(changed vold.fstab to: dev_mount usb /mnt/usbdisk auto /devices/platform/musb_hdrc

1) remount / rw: busybox mount / -o remount,rw

2) mkdir /mnt/usbdisk

3) enable nook tweaks

4) plug in drive and =)

Is there a way to make it so I don't have to manually create the mount point and be able to not have to do step 1 and 2?

Thanks.

Update:

Just found post that say I have to wait for next update to have it hold pass reboot.

New question:

Anyone know of a 8 or 16 GB usb drive that works without a hub? Want to be able to load movies on it so I can pull new ones over during long plane flight.

Thanks.
[Nook Color Android Development] mrmark93:
What about this combo:
[Nook Color Android Development] jinp6301:
still having the same problem

I have no idea whats wrong with it because it seems like its working?

Here's the dmesg

http://pastebin.com/L5qkB7pt
[Nook Color Android Development] verygreen:
-71 is "Protocol error". I often get these if I use unpowered hub and the device I attach is too power-hungry.

It seems you get timeouts (-110) doing IO to your SD card too, overly slow SDcard? This is not a good sign though might be irrelevant for the USB problems.
[Nook Color Android Development] jinp6301:
Thanks for the explanations! I'll have to try a powered hub. And the card I have is a class 6 kingston. Shouldnt be having those problems :( I'll try moving files onto the emmc.
[Nook Color Android Development] verygreen:
You really need to look into class4 Sandisk.

Read this: http://xdaforums.com/showthread.php?t=1005633
[Nook Color Android Development] newellj79:
Anybody had luck mounting a android phone as a storage device?
[Nook Color Android Development] allerretour38:
Hello,

Trying to get my dream of making Skype calls working, and I think I'm close. Hoping that someone can tell me what I'm doing wrong.

I'm running CM7 off of an SD card, using verygreen's image in the first post of the "Size-agnostic SD Card image ..." thread.

I think I have the latest nightly build: cm_encore_full-124.zip

I'm using the Nook USB Host Switcher app.

The usb is working on some level, because:

a) I can plug in an optical mouse and - sure enough - I get the mouse arrow and can move around, click on apps, etc. I'm not using a hub (powered or otherwise) with the mouse; I just plug it straight into the adapter.

b) I'm using this device to try to get my normal audio jack headphones to work.

http://cgi.ebay.com/USB-2-0-3D-AUDIO-SOUND-CARD-VIRTUAL-7-1-CH-ADAPTER-/190530137002?pt=LH_DefaultDomain_0&hash=item2c5c7b2baa

The device is recognized at some level, because the power light comes on when I plug it in AND those volume control buttons work. That is to say that I can raise and lower the output speaker volume on the NC using that sound card adapter. So the Nook is recognizing it at some level, but I can't get the mic recognized at all. I've tried using both the Voice Search app and the Skype app, but neither works. Voice Search gives me an "audio problem" message, and Skype just doesn't work.

I see that a couple of people have posted log output which seems to give an indication of what's going wrong. Can someone tell me where I can find that? Also, is there a real basic voice app that I can use to do testing on? One that someone else has already confirmed CAN work?

Thanks much.
[Nook Color Android Development] lschroeder:
I tried a few post back. VG has a special kernel that you need plus an audio file that you need to add using an app like root explorer (these are back quite a few posts and not on the OP). I was using Racks installer for phiremod v7 Test with these items plus I used Racks method for installing Dal's OC kernel. I probably should have been using VG installer with a recent nightly and no OC kernel. You have to replace the kernel manually and Racks version was giving me problems, so I temporarily quit. Good luck! I might try again with a backup image of of an updated nightly on VG sdcard (my current VG nightly 122 sdcard has OC kernel).
[Nook Color Android Development] allerretour38:
Thanks for the reply. I believe that the audio files that you're talking about are alsa.omap3.so. I saw the post saying that you had to drop them in /system/lib/hw, but I saw that they were already present, so I figured that they had already been integrated into whatever system/build I was using. Or am I supposed to replace the existing file with a new version?
[Nook Color Android Development] lschroeder:
Not sure, I never got it to work. I did paste it in mine. How about replacing the kernel with his special kernel for skype? Did you also do that?
[Nook Color Android Development] verygreen:
You need to rplace the file, the existing version is buggy + does not have microphone support at all.

I would also recommend to install the kernel referenced in that same post or the behavior of apps trying to use microphone when nothing is connected would be strange (skype hangs for one).

I do my testing with skype and it works.

Voice recorder does not work (as in, the sound recorded is quite strange), but I did not look too much into it.
[Nook Color Android Development] lschroeder:
I am using your sdcard with nightly 122, Dal's OC 06/30. Can I make a backup image of my sdcard, when mounted in a pc, replace Dal's OC kernel with yours, boot, use root explorer to to replace existing other mentioned file, and use Nook USB Host Switcher from my powered hub to activate Logitech USB Headset H360. I guess I need a skype app also?
[Nook Color Android Development] allerretour38:
Thanks both. OK, I will replace the alsa file; I assume that I can just copy it on to the SD card in the right place.

I'm not sure what I have to do to install the kernel though. Do I just copy it to /boot and reboot, like for the nightly builds? Or is it something else? I found this instruction for installing a kernel to an SD card in the "Dalingrin's OC kernel" thread.

if flashing to sdcard:

adb shell mount -t vfat /dev/block/mmcblk1p1 /emmc

adb push uImage /emmc/uImage

adb remount

adb push system /system
​

I guess I'll try just copying to /boot and rebooting first, and then see if that works. If anyone can advise, I'd appreciate it. Thanks.
[Nook Color Android Development] verygreen:
Yes, you would need skype if you plan to use a microphone (other voice app might also work but untested).
[Nook Color Android Development] verygreen:
In case you cannot read the commands I typed in the video, you do this (in bash):

mount /dev/block/sda1 /mnt/SOMEWHERE

and then /mnt/SOMEWHERE is where it is mounted.

don't forget to create /mnt/SOMEWHERE beforehand (might need to remount root RW).

Just make sure your cmera can self-power in this mode instead of relying on the host providing the power (and certainly hope that it does not try to charge over USB).

Does not your camera have a screen of its own? ;)
[Nook Color Android Development] verygreen:
Imagine what I went through first spending money on a new toy (nook), then finding out I need a special usb cable, then BT headset...

But it's fun too. I guess if you want to have some fun, be prepared to spend some money ;)
[Nook Color Android Development] Arbelzapf:
Hmm...I get an "invalid argument" when trying to mount my external hard drive. It does show up in /dev/block/ and I did create the mountpoint first. root is mounted in rw.
[Nook Color Android Development] verygreen:
Check dmesg to see what is it complained about?

Specify the filesystem type (-t whateveryourfs) if it's not just fat. e.g. if you have ext4 there the default would try ext3 and fail due to incompat features and you need to use -t ext4 to overcome the problem.
[Nook Color Android Development] FRSP:
Obviously this is deeply in experimental territory as you say right now, but whenever someone gets around to making a user-oriented version, it might be a good idea to have a VBUS warning in the status bar while it's active.

Some experiments with a current limiting resistor and metering might be informative. But is there any proposed scheme by which it could detect and switch off?

Perhaps automatically powering down VBUS whenever the USB device is unplugged would work. The methodology would be plug in USB device, use status bar button to enable VBUS, disconnect USB device - automatic VBUS disable. Plug in new USB device, manually activate VBUS again. And of course it should refuse to activate if it detects an external supply. Perhaps a dev more familiar with android user mode work could help with this.

Hmm, automatic VBUS disable might make devices that re-enumerate fail? Especially clever embedded gizmos that only assume their real identity after a firmware download? Option to enable a short delay?
[Nook Color Android Development] Mistar Muffin:
I had the same thought about automatically powering down the vbus upon device disconnect. Sounds like a good solution if it is possible.
[Nook Color Android Development] Divine_Madcat:
Ah... gotcha. Sorry about asking - here at work, i have to make the YT videos kinda small so no one notices. My apologies for a redundant question (and doubly so for asking one that i realize now i should have known anyway.. lol)

Oh, its power source is all on board (a vertical grip packing two Li-ion batteries).. :)

As for the screen - sure, it has one, but i love my Nooks 7" IPS as opposed to a 3" built in. Ideally, i need something that can open RAW files (which would be amazing, but i don't think its out there for my Sony yet), but Jpeg viewing on the larger screen is still preferable. All too often, something looking in focus on the small screen, may be just off on a bigger screen, and at that point, i have lost the chance to retake the shot.
[Nook Color Android Development] Arbelzapf:
This is what dmesg says when I plug it in:

<7>[ 6123.342498] usb usb1: usb resume
<7>[ 6123.359710] hub 1-0:1.0: hub_resume
<7>[ 6123.363739] hub 1-0:1.0: port 1: status 0101 change 0001
<7>[ 6123.475006] hub 1-0:1.0: state 7 ports 1 chg 0002 evt 0000
<7>[ 6123.481048] hub 1-0:1.0: port 1, status 0101, change 0000, 12 Mb/s
<6>[ 6123.592132] usb 1-1: new full speed USB device using musb_hdrc and address 10
<7>[ 6123.719055] usb 1-1: ep0 maxpacket = 8
<7>[ 6123.728302] usb 1-1: skipped 1 descriptor after interface
<7>[ 6123.734558] usb 1-1: skipped 1 descriptor after interface
<7>[ 6123.740539] usb 1-1: skipped 1 descriptor after interface
<7>[ 6123.746368] usb 1-1: skipped 1 descriptor after interface
<7>[ 6123.752532] usb 1-1: default language 0x0409
<3>[ 6123.759704] usb 1-1: device v045e p028e is not supported
<7>[ 6123.765441] usb 1-1: udev 10, busnum 1, minor = 9
<6>[ 6123.770690] usb 1-1: New USB device found, idVendor=045e, idProduct=028e
<6>[ 6123.777923] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
<6>[ 6123.785705] usb 1-1: Product: Controller
<6>[ 6123.789978] usb 1-1: Manufacturer: Microsoft Inc.
<6>[ 6123.795196] usb 1-1: SerialNumber: 10E7F90
<7>[ 6123.802856] usb 1-1: uevent
<7>[ 6123.811004] usb 1-1: usb_probe_device
<6>[ 6123.818054] usb 1-1: rejected 1 configuration due to insufficient available bus power
<4>[ 6123.829528] usb 1-1: no configuration chosen from 1 choice
<7>[ 6123.835876] drivers/usb/core/inode.c: creating file '010'
<7>[ 6123.842102] hub 1-0:1.0: 92mA power budget left
<7>[ 6123.848297] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002
<7>[ 6123.854339] hub 1-0:1.0: port 1 enable change, status 000001
[Nook Color Android Development] ADude:
So, what is the overall status of Audio Input for the Nook Color ?

For example, many of the aforementioned Microsoft USB cameras have microphones.

Thanks !
[Nook Color Android Development] verygreen:
Much better controlling app is in the plans, like I said. My android programming experience is 0 and the app you see is the first for me ;)

Sorry, I am a software-only guy, I don't do hardware.

Yes, this is essentially my plan if the frying issue confirms. I'll implement it at kernel level just to be extra sure.

The good news is if ou can bring external 5v to drive vbus (a battery pack or whatever), a different mode could be enabled where vbus is driven by the external power and nook would be able to charge from it at the same time while working as usb host (basically what hololight demonstrated).

It' not yet clear if we need to do any of this or not. Once confirmed we can work out the implementation kinks.
[Nook Color Android Development] :
I'm interested as well. Forgot I have an M$ webcam. Will plug in when I get home.
[Nook Color Android Development] verygreen:
For raw files you can run real linux like Fedora (I am working on a port) or Ubuntu. ;)
[Nook Color Android Development] verygreen:
So the MS controller wants to draw more that 100mA... Try with a powered hub, I guess.
[Nook Color Android Development] racks11479:
What the?! Did I read right?! lol

And I thought you mistyped your PM earlier...

I'll be keeping my eyes open :eek:
[Nook Color Android Development] FRSP:
Yes, the "off" would be in the kernel. But it would be nice if the "on" signal to the kernel were eventually triggered by a button next to the wifi, etc toggles CM has in the status bar expansion, which is user mode stuff.

Can the nook be convinced form the software side that it has a high current charge source available? Or would the external supply need a momentary pushbutton to short its data lines?

I'm thinking a little bit about how to do a safe hardware test, problem is every time I play with a different android version it takes numerous attempts to get my current install stable enough for general use again. Restoring from a backup image is a little better, but even simply rebooting seems to often break it to a mode where it crashes and runtime-start-loops or kernel reboots every minute or so.
[Nook Color Android Development] rhcp011235:
Very Cool.

I will get this out.
[Nook Color Android Development] seth.i.simmons:
Holy crap, I would love to be able to run some Fedora on here, that would be insane! VG, you are the man.
[Nook Color Android Development] poofyhairguy:
Um guys, lets fill up verygreen's Thanks Meter. More than six months after release our Nook keeps getting new capabilities thanks to the hard work of the CM7 team!!!
[Nook Color Android Development] ADude:
Why - what would that get you on the NC that you would not get with Ubuntu ?
[Nook Color Android Development] verygreen:
What would you need this for?

It is possible to make the charger to open the battery gates.

The battery voltage itself is not enough to drive the vbus without external 5v source, though. At least not enough to start, once the external source kickstarts the bus, then battery seems to be enough to drive it later on until disconnect.

If you have a spare microSD card, use my installer referenced from the first post to install a fresh nightly, then install updated kernel on top of it, install the app and off you go, your normal image would not be affected.
[Nook Color Android Development] verygreen:
Yes, just copy it instead of the file already there.

Just copyign to boot will work (the method above is doing exactly that anyway)
[Nook Color Android Development] allerretour38:
Humm, well, it might work great. Installed the new kernel and the new alsa file, and the first thing I noticed is that the mouse doesn't work anymore. Plugging in the mouse caused the Nook to freeze (I tried it several times), so I guess the new config (kernel and alsa file) is for audio, but not for other h/w (or at least, not for mice).

I then tried the headphones using my audio sound card adapter. Could make a Skype test call and it sounded great on my headphones, but no recording through the mic. The thing is though, as a test, I tried using the same sound card adapter on Skype through my computer, and I'm not getting any recording there either. So maybe there's a problem with this adapter, not the Nook setup. I'm going to keep experimenting and see what i can find out.
[Nook Color Android Development] lschroeder:
Glad to hear that you are making some progress. Gets me motivated to try again.
[Nook Color Android Development] :
From: http://cm-nightlies.appspot.com/?device=encore

[CENTER]to be included in next nightly:[/CENTER]
USB Host: USB mass storage device mount point (android_device_bn_encore)

Good News!!!
[Nook Color Android Development] chisleu:
Very cool indeed! I have a wall-powered Thermaltake USB3.0 SATA3 enclosure with a Seagate Baracuda XT 2TB SATA3 7200rpm drive in it.

It screams (100+MBps write speed) and even at the slower speeds on the NC, it should be plenty fast enough to stream movies/music!! Very excited about this! :)
[Nook Color Android Development] allerretour38:
More progress. Using my desktop, I verified that my audio device was functioning, although I also found out that I had to boost the mic input volume quite a bit to make it useful. So, back to the Nook, and I tried to look for anywhere where I could boost volumes. The only place I could find anything was in Nook Tweaks, where I put the headphone analog gain to maximum. I wanted to try the DAC boost setting also, but it just stays at zero (actually, it lets me change it, but the new settings don't stick; it's always back to zero when I re-check it). I thought that there might be something in the Nook Tweaks->USB settings, but it says that my kernel is not compatible. So anyway, with the headphone analog gain set to max, I tried Skype again. Once again, sound through the headphones sounds great, and this time I could hear myself, although it was choppy (not horrible though; usable I think) and very, very faint. It definitely worked though. Placed a test call and had my own voice played back to me. Now I have to find a way to boost the volume on the mic. On Ubuntu, I'd run that alsa thing and play with the settings there. Don't laugh at me, but there's no way to do that here is there?
[Nook Color Android Development] verygreen:
Try using alsa_amixer to adjust the mic boost on your device (from terminal emulator).

The mic input IS somewhat unclean and choppy. My theory is this is due to some strange rate conversions between what mic provides and what voice-in apps want.

Android is a big mess in sound department, so far I have not figured how to make it better, but at least it's usable enough for skype calls.
[Nook Color Android Development] allerretour38:
Tried alsa_amixer, but I get

amixer: mixer attach default error: no such file or directory

I googled a bit, and it appears as though I have to run this as root. If I try to "sudo" it though, I get:

"sudo: permission denied" (same thing with sudo su)

I thought maybe I could add Terminal to the Superuser app, but I don't see a way to do that. Any idea on how I can run this alsa_amixer as root? Muchas gracias.
[Nook Color Android Development] verygreen:
just use "su"
[Nook Color Android Development] allerretour38:
Thanks. That worked. Now I've got to do some fiddling.
[Nook Color Android Development] Divine_Madcat:
Thats what she said.... ;)
[Nook Color Android Development] chumpster:
Nightly 126 is suppose to have support for USB memory. Has anyone tried it? Any impressions? Does it auto-mount?

I am stuck at work so I won't be able to try it for another 8 hours. But I curious about the results...
[Nook Color Android Development] lschroeder:
I have the complete setup going, nightly 122, OC 06/30, and nook tweaks 1.3.8. Just played an mp4 with default movie player from 16GB Flash Voyager USB drive. Looked great! Using the Storage settings Additional storage:mnt/usbdisk. Just did unmount from this menu, now plug in fat 32 1TB hard drive that is in the notification as Preparing SD card Checking for errors.

After several minutes turned to USB storage device mounted. Settings has Total space .91TB, Available space 630GB. Just used music app trial PowerAMP to scan a music folder on TB drive and play music from one of my albums. Switch to yxplayer Neon video player to blow up Lawrence of Arabia on 1TB I originally recorded for iPodtouch to acceptable size without stretch effect other video players have for nook.

I also have wireless usb adapter for Logitech LX710 keyboard and wireless mouse. Works great, mouse and keyboard! Using Belkin powered 4 port hub with y cable for data and power.

Just plugged in my Logitech USB Headset 360. Previously VG said we need to change 1 file and replace kernel to get working with skype. I did not do either yet. Only thing that works are the volume control on the headset. Any suggestions here?

Edit: Just replace alsa.omap3.so and rebooted. Now my usb the head phones in the Logitech USB Headset 360 work. I just tried google Voice and now the mike is working also !!!!!!

VG: "The other important bit is the alsa.omap3.so: http://nook.handhelds.ru/usbaudio/alsa.omap3.so

Drop it to /system/lib/hw/ (this on sdcard this is partition2, /lib/hw)" copied to my nook and then used Root Explorer to overwrite the current one.

Anybody else got mike and usb speakers working?
[Nook Color Android Development] bled82:
I just installed 126 but cant seem to get drive to mount the light on it does not light , it was on before with the cm 7 rc1 and the tweak but now it does not power on and i see the option in setting that shows a mount point for thew drive but dont see how to enable the drive please help
[Nook Color Android Development] lschroeder:
When trouble shooting I like using my powered hub. It rules out power issues and the lights show when I use Nook Tweaks to turn on. By the way, from the market I just downloaded version 1.3.8. See my post above yours, I guess I am lucky, so far everything that is suppose to work seems to be working. What version of Nook Tweaks are you using? Does a usb keyboard work?
[Nook Color Android Development] bled82:
ah looks like i need the OC 6/30 , looked at post maybe i have not had enough coffee today but where is the download link ? i thought i had it ill look in my downloads .

NM: I found the OC kernal i was looking for flashing now will. update after .

OK works now that i have the 6/30 kernal installed mounts without issue , after unmount is there a way to clear the sdcard notification that says " SD card removed. Insert a new one. "
[Nook Color Android Development] allerretour38:
These were the values in my alsa_amixer

I put the "HP Analog Volume" to 50%, and then 80%, and I can now hear the playback clearly. Contrary to what I originally thought, it's too choppy to use. The thing is, it seems to me that the quality is OK when it's not cut off or broken. If there was a constant problem with the rates, wouldn't the sounds quality be continuously bad? Anyway, I'm going to try a few more values to see what happens.
[Nook Color Android Development] Phatdawg:
Are you connecting these via mini usb to female usb cable?
[Nook Color Android Development] lschroeder:
See 5 post back where I have with nightly 122, OC 6/30, Nook Tweaks 1.3.8 with VG's alsa.omap3.so sub mike and speakers working.

I got skype working. Create an account with my nook. Had my friend call me. Audio and my mic were crackly. Now I will have to learn how skype works and how to tweak it with the nook. I guess that was your question.
[Nook Color Android Development] allerretour38:
I looked at your post, but what are you suggesting? That I use a powered hub?

What's your sound quality like? VG said that his sound was choppy, which he attributed to different conversion rates (I think. He's way beyond me here). My mic gives very choppy recording also. Are you saying that yours is good?