Database Users

linux on htc magician

i've been trying to find who is working on this project?
whats the updates?
where are the updates??
i have found only old post and threads about this
and old download links.

I am working on the kernel, but we need some more people for userspace support (be that android, openmoko, or just plain and simple angstrom images - making dialer and sms applications etc. work). The best place to get current information about linux on magician is the #htc-linux IRC channel on freenode.net.

cool
ok cool i dont have much time to dedicate now as i'm involve with other projects i may be able to help you with userlands at the end of the year i pm you when i'm ready
really excited about this

This project has died ? or?

andor44 said:
This project has died ? or?
Click to expand...
Click to collapse
nope just lacking someone for the userland
ph5 is working on the kernel

How is the kernel going i would like so see linux run on magican

check
http://forum.xda-developers.com/showthread.php?t=369149
something going on there

lock n' load marines ;-)
I know my way around tweaking/hacking HW to get working under linux...
did to few times back with some stuff on adestop PC.
1. I need a running kernel
2. A terminal
3. SDK and IDE for userland tools (GNU suite)
4. A ipk repository to leech from
5. duded and fellows of all sorts
6. time
Already done for the 1 and partly for the 2
shall we?

progress
although i liked qtopia better, i put that Armostrong thingie (foun in the tmp folder of our ftp server here...
The kernel is 2.6.21 hh20
1. and it boots to the gui
2. it let make me calls (777 answered right)
3. it shows incoming calls (although won't pick up the hook)
4. It begun showing messages (half way through upgrade)
5. It has ateminal and a touch type keyboard (querty lol)
6. it let me define usb0 network device
7. It let me log in via ssh as root (pasword is empty: just hit enter)
then i fiddled with the ipkg tool:
I managed to let it run trough squid proxy when i couldn't make it route...
file: /etc/ipkg.conf
Code:
# Must have one or more source entries of the form:
#
# src <src-name> <source-url>
#
# and one or more destination entries of the form:
#
# dest <dest-name> <target-path>
#
# where <src-name> and <dest-names> are identifiers that
# should match [a-zA-Z0-9._-]+, <source-url> should be a
# URL that points to a directory containing a Familiar
# Packages file, and <target-path> should be a directory
# that exists on the target system.
# Proxy Support
#option http_proxy http://proxy.tld:3128
#option ftp_proxy http://proxy.tld:3128
option http_proxy http://172.31.0.3:3128
option ftp_proxy http://172.31.0.3:3128
#option proxy_username <username>
#option proxy_password <password>
# Offline mode (for use in constructing flash images offline)
#option offline_root target
dest root /
lists_dir ext /var/lib/ipkg
172.31.0.3:3128 is the URL of my proxy - edit as appropriate before storing to the sd card
If all goes well i promise...
... i make an image (128MB) of the whole SD card i used...
;-)

Ah harrr sharky
a thought beastie this one !
got to see the end of the upgrade of ipkg and got the device hang...
another hard reset ahoy
:-(
see if it boots again?
(stay tuned...)

at least it boots...
no X this time ?
just the blank screen...
have to troubleshoot

???? got a funny menu on the screen and couldn't get pass it?
boy a wish someone here had any clue

cest73 said:
???? got a funny menu on the screen and couldn't get pass it?
boy a wish someone here had any clue
Click to expand...
Click to collapse
it seems it has problem with default calibration:
the X appears but the calibrator fails :-(
EDIT:
nope, it was DBUS - failing to start due of missing users!

was a bit offline these days my magician is broken some stupid chip burn out after years of good service i ve sent it to taiwan for repair but i have little hope
i ll see if i can buy another one on ebay these days
we should talk on irc one of these days cest73 (althought i am usually online at weird hours)

elivildarkknight,
Im +01h off Greenwich, so we shall try it?
OTOH:
the main issue regarding useable Liunx is:
1. A fast hard-reset able ROM (bare 2003SE) [i don't have now]
2. A SD card reader [i have]
3. A decent image of a working kernel [have the 2.6.21 hh20 of Armstrong's 2008.1]
4. A way to make magician respond to a ssh log in upon USB connect [i seek the way right now]
5. A decent userspace stack able to bring all magician's HW to life [once we can make it 'network']
6. A decent environment before the X or any WM is started for fallback [this can be done IMHO]
7.

try to get in touch with phillip zabel he is working on the kernel and can help you on the image there is a working qtopia image floating around you can try to see the config they used for the display and other stuff a booting kernel with an image on sd should be ok for a start
the developers of blueangel also may help i ll try to see who is working on there image
i'm at +5 GMT the main problem is that i have few free time because of exams and real life
my magician is going to Taiwan for repair now so i m left with the hermes right now
will be happy to help you anyways
in april i'll be more on irc try to keep us update on your work

roger to that
ok
we shall take the time then...
i thought about a ncurses based teminal keyboard emulation controlled with the jog dial...

continued troubleshooting for magician...
it appears i miss the calibration procedure somehow
As i can't use it as a normal phone under moko yet, i'm limited for how long i'm able to play with it...
I will try again today to get at least something launched over that X...
I somehow like more the QT stack?

progress report...
My distro is Slackware so i found this:
http://wiki.openmoko.org/wiki/USB_Networking#Slackware_.28tested_with_12.1.29
Does not even work, but the page was useful:
When i connect the Magician while running Linux, i get to a terminal and become root:
Code:
# dmesg
there i see that usb0 is now available:
Code:
usb0: unregister 'cdc_subset' usb-0000:00:1d.1-2, Linux Device
usb 3-2: new full speed USB device using uhci_hcd and address 19
usb 3-2: configuration #1 chosen from 2 choices
usb0: register 'cdc_subset' at usb-0000:00:1d.1-2, Linux Device, 16:ce:a6:75:bd:58
usb 3-2: New USB device found, idVendor=0525, idProduct=a4a2
usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 3-2: Product: RNDIS/Ethernet Gadget
usb 3-2: Manufacturer: Linux 2.6.21-hh20/pxa27x_udc
so i manually bring up the usb0 from my host:
Code:
# ifconfig usb0 192.168.0.200
# ifconfig usb0 up
# ping 192.168.0.202 -c4
PING 192.168.0.202 (192.168.0.202) 56(84) bytes of data.
64 bytes from 192.168.0.202: icmp_seq=1 ttl=64 time=1.25 ms
64 bytes from 192.168.0.202: icmp_seq=2 ttl=64 time=1.96 ms
64 bytes from 192.168.0.202: icmp_seq=3 ttl=64 time=1.76 ms
64 bytes from 192.168.0.202: icmp_seq=4 ttl=64 time=1.56 ms
#
You have to know the rest for the routing to the internet to be successful...
i hope this helps a bit?

adding the parameter
Code:
psplah=false
to the default.txt:
Code:
set KERNEL zImage
set CMDLINE "root=/dev/mmcblk0p2 console=tty0 rootdelay=1"
bootlinux
to be:
Code:
set KERNEL zImage
set CMDLINE "root=/dev/mmcblk0p2 console=tty0 rootdelay=1 [U]psplah=false[/U]"
bootlinux
disables the nice spalsh screen while boot-up, allowing one to see why the darn thing is hanging...

Mounting the Xoom in Linux (as well as adb)

The xoom can mount just fine on Linux but it is an MTP not a Mass Storage device.
Disclaimer: I am not responsible for any damage to your device, computer, relationship, etc.... The following is meant as a guideline and worked for me but as always use your head.
I did this on my Kubuntu Maverick laptop, but it should apply to most *buntus plus debian. Other flavors should be similar, post a request and I will help if I can. I am familiar with Suse and RHEL/Centos as well but beyond those it will be guess work.
The first thing I would recommend doing is making the device read/write to normal users.
Code:
sudo touch /etc/udev/rules.d/51-android.rules
echo "SUBSYSTEM==\"usb\", SYSFS{idVendor}==\"22b8\", MODE=\"0666\"" |sudo tee -a /etc/udev/rules.d/51-android.rules
sudo /etc/init.d/udev restart
NOTE: This also "fixes" adb so it is useable with the xoom as a normal user. If that is all you want you can stop here.
NOTE 2: You could also set an OWNER rather than changing MODE but I chose the most common route for this example/
Now install either mtp-tools or mtpfs for mounting using FUSE. Since I went the fuse route that is what I will conver here. (I installed the mtp-tools package but beyond using it to debug getting mtpfs to work I have never used it before.)
Assuming you already have fuse configured, for (k|x)ubuntu or debian :
Code:
sudo apt-get install mtpfs
If you do not have fuse already configured then do that first. Look it up online if you have any questions. If you get stuck I will try and help but this post is not about how to configure FUSE.
After that it is simple. Plugin your xoom and from the command line type:
Code:
mtpfs mountpoint
and to dismount it
Code:
fusermount -u mountpoint
so in my case I mount it in a subdirectory under home called xoom
Code:
mtpfs /home/janetpanic/xoom
fusermount -u /home/janetpanic/xoom
I have confirmed moving files to and from the actual directories but not from the meta "playlists" directory. I hope that helps...
EDIT: Fixed Typo... had "(idVendor)" instead of the correct "{idVendor}"

Thanks for sharing your workaround. Unfortunately, it's no joy here. After following the procedure described, the terminal returned no error, but on trying to open the Xoom directory via Nautilus, I received the following message:
Code:
Error: Error stating file '/home/sog/Xoom': Transport endpoint is not connected
Please select another viewer and try again.
Unmounting proceeds without error.
Distribution: Ubuntu Lucid x64

Did you connect your xoom before or after you mounted? The most likely problem is the undeveloped configuration .
Change the line in 51-android.rules to
Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="22b8", SYMLINK+="libmtp-%k", MODE="0666"
[\code]
Restart udev and then do a "ls -lah /dev/libmtp*" with the device attached and list the output. I need to figure out if the problem is the udev rule or elsewhere.
If the ls does not show any files then send the result of "lsusb |grep Motorola" which better list a line or there is something weird going on.
Sent from my Xoom using XDA App

Updated 51-android.rules as directed, then:
[email protected]:~$ ls -lah /dev/libmtp*
lrwxrwxrwx 1 root root 15 2011-02-27 19:59 /dev/libmtp-1-4 -> bus/usb/001/004
[email protected]:~$ lsusb | grep Motorola
Bus 001 Device 004: ID 22b8:70a8 Motorola PCS

Wait, you aren't able to get the Xoom to mount as a mass storage device?
ed. The leaked Xoom manual suggests it support mass storage. Phew. You were scaring me there a bit.

as far as I know, it's been confirmed that the current stack does not support mass storage, only mtp.

sogrady said:
as far as I know, it's been confirmed that the current stack does not support mass storage, only mtp.
Click to expand...
Click to collapse
Which stack, Linux or Honeycomb's? Where is it confirmed?
Non-working mass storage is a potential deal breaker.

honeycomb's. see here or here for details.

Thanks for the links.
This is a real WTF.

Can someone try running this attached apk to see if it enables mass storage? (It just runs enable, it won't run disable, so I don't know what will happen, it might cause apps to crash but rebooting should fix it, standard disclaimers apply, you run this at your own risk, etc., etc., etc.)
I don't have a Xoom, otherwise I'd try this myself.
Relevant code snippet for those interested:
Code:
StorageManager s = (StorageManager)getSystemService(Context.STORAGE_SERVICE);
Class c = s.getClass();
Method m = null;
try
{
m = c.getMethod("enableUsbMassStorage", (Class[]) null);
m.invoke(s);
}
catch(Exception e)
{
// TODO Auto-generated catch block
e.printStackTrace();
}
There may even be an easier way to achieve this -- I can't verify for myself because Honeycomb isn't in AOSP -- it doesn't work in the sim, but it might on a device: run adb shell, then run "am start -n com.android.systemui/.usb.UsbStorageActivity".

ydaraishy said:
Can someone try running this attached apk to see if it enables mass storage? (It just runs enable, it won't run disable, so I don't know what will happen, it might cause apps to crash but rebooting should fix it, standard disclaimers apply, you run this at your own risk, etc., etc., etc.)
I don't have a Xoom, otherwise I'd try this myself.
There may even be an easier way to achieve this -- I can't verify for myself because Honeycomb isn't in AOSP -- it doesn't work in the sim, but it might on a device: run adb shell, then run "am start -n com.android.systemui/.usb.UsbStorageActivity".
Click to expand...
Click to collapse
I ran the activity manager command and it brought up the usb mass storage screen but did not mount on computer. Also ran the apk but did not mount. Awesome job though. keep fighting the good fight

sogrady said:
Updated 51-android.rules as directed, then:
[email protected]:~$ ls -lah /dev/libmtp*
lrwxrwxrwx 1 root root 15 2011-02-27 19:59 /dev/libmtp-1-4 -> bus/usb/001/004
[email protected]:~$ lsusb | grep Motorola
Bus 001 Device 004: ID 22b8:70a8 Motorola PCS
Click to expand...
Click to collapse
Well that is interesting . You have read write privileges on the xoom. Sounds like it is a fuse configuration issue. Do you have any other fuse file systems you run?
Sent from my Xoom using XDA App

bigrushdog said:
I ran the activity manager command and it brought up the usb mass storage screen but did not mount on computer. Also ran the apk but did not mount. Awesome job though. keep fighting the good fight
Click to expand...
Click to collapse
Damn it. Looks like I actually need a device to get it working, and the AOSP drop. It's so moronic why they disabled mass storage.
Hmm. Can someone run, from adb shell, the output from "mount", and "ls /sys/devices/platform" for me?

Never mind. Mass storage has been defined out of the stingray (Xoom) kernel. It's not even in the default kernel.
To get mass storage support, be prepared to build your own kernel and reflash the device (once that's done, the am command above or the enabler app will work properly).

I've founded a working(ish) solution. This Xoom forum post details an approach that permits transfer of video/music/etc to the Xoom via Linux.
Couple of caveats:
1. The gnomad2 application is very unstable. Crashes frequently.
2. It appears to be write-only: I have not been able to delete files from the Xoom using this interface.

Thanks for the instructions to connect to a xoom tablet via Linux! However, I'm using Opensuse 11.3 and 11.4 on two different systems. I did install the mtp-tools with no issues, however, there is NO file by the name of mtpfs. A search on the net does not reveal it either. Where do I get this, or what package is it part of? Thanks again. If I can't get this tablet to connect to my linux box, I will have to take it back, since I do NOT use winbloze or Mac. Pretty short sited of Motorola IMHO.

Personally, I've given up on MTP + Linux Combo. I just use a straigt FTP transfer over wifi ( FTP Server on tablet ). It's about the same speeds.

any headway on this...
i am getting the: Transport endpoint is not connected error still and i have no real experience with FUSE so im stuck to using windows for any transferring.

stlsaint said:
i am getting the: Transport endpoint is not connected error still and i have no real experience with FUSE so im stuck to using windows for any transferring.
Click to expand...
Click to collapse
try following the directions in this thread:
http://forum.xda-developers.com/showthread.php?t=981774
They are basically a superset of what I posted. If you still have trouble after that post in either thread (this one or that one) and I will try and help as best I can.

followed the thread up unto the fstab part as i dont wan to edit my fstab without confirmation that it will work. But i get the exact same error with the endpoint text. I am trying this on Crunchbang linux which is based off debain the same way ubuntu is. I am probably going wrong with FUSE somehow but i have never messed with it so i dont know how to troubleshoot it.

ADVICE/SUPPORT : UVC Camera on Samsung Galaxy Tab 10.1- No device Node??

HI,
I am trying to interface the UVC Camera to the Samsung Galaxy Tab 10.1(GT-7510) , but I am not able to see the device node getting created in the shell( I have installed the Linux terminal Shell Application) and rooted the device using this Video .Can somebody plz tell/advice how I can achieve it and access the device Node or at-least get it created.
Following is the log on dmesg :
usb 1-1 new high speed USB device using tegra-ehci and address 97
hub 1-0:1.0 unable to enumerate USB device on port 1 ,
usb 1-1:device v0ac8 p3420 is not supported
On My Laptop I get this output on Dmesg :
[12307.364237] uvcvideo: Found UVC 1.00 device Venus USB2.0 Camera (0ac8:3420)
[12307.366108] input: Venus USB2.0 Camera as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.1/2-1.1:1.0/input/input14
[12308.537059] usbcore: registered new interface driver snd-usb-audio
also i can see the camera getting blinked on connection which proves that it is getting the power-supply and getting connected with the system.
I think there is a support for UVC USB devices in the kernel (not sure) otherwise I am ready with the Kernel For Samsung Tab 10.1 (GT-7500 (Higher Version: GT-7510)) from here .(GT-P7500_MEA_Opensource.zip (requires Login).
Plz assist.
Rgds,
Softy

You seem to know a bit about what you're doing. I'm not really familiar with this device. I did a search and did not find anyone who has don't this yet. The first priority is to get a Linux device in /dev/ folder. This is generally handled by a device driver and a udev rule. Try the newer kernel if you can. The android 4.0 ics has a Linux 3.x kernel. See if switching to ics helps. Try compiling a custom kernel with all modules. Once you have a device, try using SSH or sftp from your desktop under Linux to stream from that device with vlc or another media player.
Do you have any examples of this device in use on mobile Linux? It may require writing an entire kernel driver.

HI,
Yes that is the same line of thinking for us as well.We are trying to compile the kernel and load it .- Ongoing
I believe only the zImage is the one which is to be flashed.But I am little scared to do this.Couldn't find the instructions to loading the Zimage even though I can compile one.
Rgds,
Saurabh

softy007 said:
HI,
Yes that is the same line of thinking for us as well.We are trying to compile the kernel and load it .- Ongoing
I believe only the zImage is the one which is to be flashed.But I am little scared to do this.Couldn't find the instructions to loading the Zimage even though I can compile one.
Rgds,
Saurabh
Click to expand...
Click to collapse
Flash it with Heimdall, even if it won't work you will be still able to get into download mode of bootloader (which you aren't supposed to flash) and reflash the kernel with stock one.

USB to LAN : Trendnet TUE2-ET100

Hi everybody,
Like video said, I'm noob !
I come from french and surely I'm not the better englishman of france, but I need you and I try to resolv my problem :=)
I have iconia a500, and go with it in holidays.
In my room, only RJ45 for internet, not WiFi... And my lady NEED internet ^^
That's why I try to use this device.
But, when I try to use it... It doesn't works :=/
I've seen that with taboonay it can works but it's rom for 3.2 and I am in 4.03...
Here my configuraiton :
CWM-based Recovery v5.5.0.X(thor2002rorev1.7)
Flexreaper 5.1
I use Trendnet TUE2-ET100 for network adaptator.
Have we one rom who can help me plz ?
I wait your help if it's possible.
Thank you.

Hi,
Nobody can help me ?

It would be probably better to just buy simplest access point out there and use it as a bridge between ethernet cable and wifi . You don't even need router functionality if the tablet will be the only device used. Just buy AP, configure it and just connect the cable to the RJ45 socket and voila.
You will probably need to connect AP to the PC with a cable to configure it but you need to do this only once. You need to configure the wifi name and security (preferably WPA2 PSK).

Hi,
Thank you for you answer !
Can we resolv problem without AP ?
The reason it's that we go to hotel and I bagage is full... xD
With USB analyser software (or application), I can see one information about my LAN adaptator... But it doesn't works when I try to use it.
I don't know if one other kernel can help me or if it's with other custom ROM...
Thank you very much for your help and your solution !
But if we have other possibility it's ok for moi :=)
Merci ;=)

Try the following:
Reboot the tablet (do not connect ethernet adapter yet)
In the terminal emulator display run dmesg (you can dump it with dmesg > /sdcard/dmesg1.txt for comparison)
Connect adapter
Run dmesg again and check for differences at the end (dump it with dmesg > /sdcard/dmesg2.txt and then compare both files).
This will tell if the kernel itself is recognizing the device properly as a networking device. If it doesn't then you need different kernel or kernel module for the current one for this device.
If the device is recognized and the proper kernel module is loaded and still no connectivity then one of the following can be true:
The device doesn't send request to acquire IP from DHCP (dhcp client in the rom not configured to support other devices than the built-in ones).
The device receives the IP, but the routing is not being set so the connection is not set as a default route.
The Android itself doesn't recognize the new interface and apps cannot start the connection using Android API (OS thinks it is offline).
Unfortunatelly I don't know much about how the networking on the application level works in Android and I don't have any USB ethernet adapter to do some tesing myself. I would need to ask some friends if they have one.

Very thanks to your help and sorry for this.
Below results dmesg after plug usb adapter.
Usb 1-1: new high speed usb device number 2 using tegra-ehci
Usb...: new usb device found, idVendor=0b95, idProduct=2,
Usb... : new usb device strings: mfr=1, product=2, serialnumber=3
Usb... : product: ax88772
Usb... : manufacturer: asix elec. Corp.
Usb... : seriaonumber xxxxxx
We can see that android see usb device.
But, when i made <ifconfig>, i can see only the wlan0 interface, no eth0 or other...
Maybe i have to mount it ?
Thanks for your help.

No, you don't mount network devices .
It seems that the tablet is not loading any kernel module for this device. I've done some searching and this device requires usbnet and asix modules to be loaded. I have checked if I have those module in my a500 (running CM9) and I don't have any of them.
I think that you would need to build your own kernel with proper modules to gain support for this adapter.

OMG xD
Build my own kernel
ok ok, let's go, I have already help my father to build house, I can did it !
...
Is it difficult to build kernel ? ^^
Are there any tutoriel for this ? or I need help of xda's members ?
Like other post, thank you for your interest and your help.
Sorry to make you spend time on my case

I'm sorry but my knowledge about compiling kernels is limited to PC Linux. I've never crosscompiled kernels for ARM architecture. It shouldn't be that hard. I think that you will need the Android SDK to do that. Search the dev forum.
I've been thinking about the module itself and you probably don't even need to compile whole kernel. You just need the kernel header files for the kernel you are using and you can probably compile the module alone and then just copy it to device. But you need to ask someone that is more knowledgable in this area than me.

hello, have you managed to build module for ICS or jellybean?
i have the same USB LAN adapter (i'm french too ^^)
Hope to have a positive reply!!!
thanks

[Q] CM10 (SD card) and calibre

Has anyone gotten Calibre to see a Nook Color using CM10 alpha on a bootable SD card yet? I'm running XP on this machine, and Calibre seems to see a USB device, but does not detect it as a Nook:
Code:
calibre 0.9.4 Portable
Windows-XP-5.1.2600-SP3 Windows
('Windows', 'XP', '5.1.2600')
Python 2.7.3
Windows: ('XP', '5.1.2600', 'SP3', 'Multiprocessor Free')
USB devices on system:
[u'usb\\root_hub&vid8086&pid2937&rev0003',
u'usb\\root_hub&vid8086&pid2935&rev0003',
u'usb\\root_hub&vid8086&pid2938&rev0003',
u'usb\\root_hub&vid8086&pid2936&rev0003',
u'usb\\root_hub&vid8086&pid2939&rev0003',
u'usb\\root_hub&vid8086&pid2934&rev0003',
u'usb\\root_hub20&vid8086&pid293a&rev0003',
u'usb\\root_hub20&vid8086&pid293c&rev0003',
u'usb\\vid_046d&pid_c05a&rev_6300',
u'usb\\vid_04b3&pid_301a&rev_0200',
u'usb\\vid_04b3&pid_301b&rev_0200',
u'usb\\vid_04b3&pid_301b&rev_0200&mi_00',
u'usb\\vid_04b3&pid_301b&rev_0200&mi_01',
u'usb\\vid_04b3&pid_4485&rev_0001',
u'usb\\vid_17ef&pid_4807&rev_3134',
u'usb\\vid_2080&pid_0002&rev_0216']
Drives detected:
(0) E:\ ~ USBSTOR\DISK&VEN_NOOKCOLO&PROD_R\0123456789ABCDEF&0
(0) F:\ ~ USBSTOR\DISK&VEN_NOOKCOLO&PROD_R\0123456789ABCDEF&1
Looking for devices of type: MTP_DEVICE
Cannot detect MTP devices
MTP devices are not supported on Windows XP
Looking for devices...
u'usb\\vid_2080&pid_0002&rev_0216'
No match found in: USBSTOR\DISK&VEN_NOOKCOLO&PROD_R\0123456789ABCDEF&0
No match found in: USBSTOR\DISK&VEN_NOOKCOLO&PROD_R\0123456789ABCDEF&1
Devices possibly connected: None
I had this working with CM7 on an SD card, with the same XP machine. I do have USB mass storage enabled on the Nook, and can browse both drives (SD and EMMC) from XP.

kmz75 said:
Has anyone gotten Calibre to see a Nook Color using CM10 alpha on a bootable SD card yet? I'm running XP on this machine, and Calibre seems to see a USB device, but does not detect it as a Nook:
Code:
calibre 0.9.4 Portable
Windows-XP-5.1.2600-SP3 Windows
('Windows', 'XP', '5.1.2600')
Python 2.7.3
Windows: ('XP', '5.1.2600', 'SP3', 'Multiprocessor Free')
USB devices on system:
[u'usb\\root_hub&vid8086&pid2937&rev0003',
u'usb\\root_hub&vid8086&pid2935&rev0003',
u'usb\\root_hub&vid8086&pid2938&rev0003',
u'usb\\root_hub&vid8086&pid2936&rev0003',
u'usb\\root_hub&vid8086&pid2939&rev0003',
u'usb\\root_hub&vid8086&pid2934&rev0003',
u'usb\\root_hub20&vid8086&pid293a&rev0003',
u'usb\\root_hub20&vid8086&pid293c&rev0003',
u'usb\\vid_046d&pid_c05a&rev_6300',
u'usb\\vid_04b3&pid_301a&rev_0200',
u'usb\\vid_04b3&pid_301b&rev_0200',
u'usb\\vid_04b3&pid_301b&rev_0200&mi_00',
u'usb\\vid_04b3&pid_301b&rev_0200&mi_01',
u'usb\\vid_04b3&pid_4485&rev_0001',
u'usb\\vid_17ef&pid_4807&rev_3134',
u'usb\\vid_2080&pid_0002&rev_0216']
Drives detected:
(0) E:\ ~ USBSTOR\DISK&VEN_NOOKCOLO&PROD_R\0123456789ABCDEF&0
(0) F:\ ~ USBSTOR\DISK&VEN_NOOKCOLO&PROD_R\0123456789ABCDEF&1
Looking for devices of type: MTP_DEVICE
Cannot detect MTP devices
MTP devices are not supported on Windows XP
Looking for devices...
u'usb\\vid_2080&pid_0002&rev_0216'
No match found in: USBSTOR\DISK&VEN_NOOKCOLO&PROD_R\0123456789ABCDEF&0
No match found in: USBSTOR\DISK&VEN_NOOKCOLO&PROD_R\0123456789ABCDEF&1
Devices possibly connected: None
I had this working with CM7 on an SD card, with the same XP machine. I do have USB mass storage enabled on the Nook, and can browse both drives (SD and EMMC) from XP.
Click to expand...
Click to collapse
It is not because you are running on SD. It is because you are on CM10. The device ids for CM9/CM10 are different than CM7. See that in your log that it is looking for 2080? That is now something else. Look at my tips thread linked in my signature and look at the adb on CM9 item. This will not necessarily fix your problem, but maybe you will understand what is going on.

Thanks!
leapinlar said:
It is not because you are running on SD. It is because you are on CM10. The device ids for CM9/CM10 are different than CM7. See that in your log that it is looking for 2080? That is now something else. Look at my tips thread linked in my signature and look at the adb on CM9 item. This will not necessarily fix your problem, but maybe you will understand what is going on.
Click to expand...
Click to collapse
Thanks for this. I was able to configure the NC as a user-defined device, and it's working just fine now. For others looking here, I got this from the Calibre wizard:
Code:
USB Vendor ID (in hex): 0x2080
USB Product ID (in hex): 0x0002
USB Revision ID (in hex): 0x0216
Windows main memory vendor string: NOOKCOLO
Windows main memory ID string: R\0123456789ABCDEF
Windows card A vendor string: NOOKCOLO
Windows card A ID string: R\0123456789ABCDEF
Copy these values to the clipboard, paste them into an editor, then enter them into the USER_DEVICE by customizing the device plugin in Preferences->Plugins. Remember to also enter the folders where you want the books to be put. You must restart calibre for your changes to take effect.
It seems that 0x2080 is the new device ID, and Calibre looked for something else for the NC.

No, 0x2080 is the device ID for CM7.
To find you new device ID on the CM9/CM10, open your XP hardware manger and look for the NookColor item. In your case, it is most likely yellow with the waning, this means the driver is not installed properly.
Double-click on it and and go to Details->Property->hardwareid and your should see something like:
USB\VID_18D1&PID_2D03&REV_0216&MI_01
The 0x18D1 is your newdevice ID and 2D03 is your product(?) id.
You would need to add them to your android_winusb.inf file and 0x18D1 to your adb_usb.ini file.
Update the driver again and you should now connect to your CM10 nook.
P.S. I left out quite a bit of info at the end but you could find them in here.