Re: Nokia really screwed the pooch with the USB connection
 

You might have to shut the phone down to achieve 2.0 speeds - some have reported this but mine seems to work fine anyway.
Just don't use usb hubs.

As for not enough power to charge, it has happened once while the pc was running a CPU-intensive program.

Re: Nokia really screwed the pooch with the USB connection
 

No problems with USB charging directly from the USB data connection.

Could not use Nokia PC suite via USB cable on Windows 7 on home latop when I got the phone but this was fixed at the last upgrade last week.

My ancient office PC does not recognise the N900 when connected by USB cable, but it will connect OK for file transfers.

Therefore still unable to sync N900 with Nokia PC suite on the ancient desktop PC which also has no bluetooth so I have to synchronise to my old N95 via cable and have the N900 sync with the N95 via bluetooth.

Now all my meetings are on the N900. Sorted but it a bit of a hassle.

Re: Nokia really screwed the pooch with the USB connection
 

I have had no problems with my device. I am even able to charge and get USB 2.0 speeds from a USB hub which is daisy-chained into another hub.

Re: Nokia really screwed the pooch with the USB connection
 

There was a thread somewhere on these forums regarding the N900's ability to do some sort of negotiation for power with the USB bus it connects to, and most computers/hubs are able to work with this. But "dumb" power supplies (like a cigarette lighter adapter from your car to USB) don't have this ability...so the N900 never gets a negotiation response, and it never initiates recharging. Do some searching, might explain why you need a special charger (or a hacked one in your case) to charge from some other power source besides a computer.

Re: Nokia really screwed the pooch with the USB connection
 

Works fine for me, two different cables and 3 different computers.

I believe shorting the data-pins needs to be done to comply with the usb-spec.

Re: Nokia really screwed the pooch with the USB connection
 

Sounds like you won the prize unit.

Re: Nokia really screwed the pooch with the USB connection
 

N900 sometimes ignores USB data cable
that bug was fixed in latest, but i do not know if it has nothing to do with this usb1.1 recognizing thing.

Re: Nokia really screwed the pooch with the USB connection
 

i tested the speed for mine right now with the n900 being in mass storage mode with some quick check:

With delayed sync (the should actualy test the bus itself):

laptop ~> dd if=/dev/zero of=/media/Nokia\ N900/test bs=1024k count=100
100+0 records in
100+0 records out
104857600 bytes (105 MB) copied, 6.1257 s, 17.1 MB/s

Being mounted with sync option (should test the speed of the storage itself):

laptop ~> mount /media/Nokia\ N900/ -o remount,sync
~> dd if=/dev/zero of=/media/Nokia\ N900/test2 bs=1024k count=100
100+0 records in
100+0 records out
104857600 bytes (105 MB) copied, 41.3259 s, 2.5 MB/s




kernel output from command on the computer connected to N900:
laptop~> dmesg
[62971.967061] usb 1-4: new high speed USB device using ehci_hcd and address 6
[62972.082802] usb 1-4: New USB device found, idVendor=0421, idProduct=01c7
[62972.082827] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[62972.082846] usb 1-4: Product: N900 (Storage Mode)
[62972.082861] usb 1-4: Manufacturer: Nokia
[62972.082876] usb 1-4: SerialNumber: 372041756775
[62972.083114] usb 1-4: configuration #1 chosen from 2 choices
[62972.084205] scsi3 : SCSI emulation for USB Mass Storage devices
[62972.087127] usb-storage: device found at 6
[62972.087135] usb-storage: waiting for device to settle before scanning
[62973.087866] scsi 3:0:0:0: Direct-Access Nokia N900 031 PQ: 0 ANSI: 2
[62973.088334] sd 3:0:0:0: Attached scsi generic sg1 type 0
[62973.109172] scsi 3:0:0:1: Direct-Access Nokia N900 031 PQ: 0 ANSI: 2
[62973.109506] sd 3:0:0:1: Attached scsi generic sg2 type 0
[62973.115205] usb-storage: device scan complete
[62973.116413] sd 3:0:0:1: [sdc] Attached SCSI removable disk
[62973.123085] sd 3:0:0:0: [sdb] Attached SCSI removable disk
[62979.551831] sd 3:0:0:0: [sdb] 56631296 512-byte logical blocks: (28.9 GB/27.0 GiB)
[62979.552321] sd 3:0:0:0: [sdb] Assuming drive cache: write through
[62979.553561] sd 3:0:0:0: [sdb] Assuming drive cache: write through



The messages I get on the N900 when being connected are:

N900~> cat /proc/driver/musb_hdrc
Status: MHDRC, Mode=Peripheral (Power=f1, DevCtl=99)
OTG state: b_peripheral; active
Options: musb-dma, otg (peripheral+host), debug=0 [eps=12]
Peripheral address: 06
Root port status: 00000100
Gadget driver: g_file_storage

ep0 (hw0): 1buf, csr 0000 maxp 0000
(queue empty)

ep1in (hw1): 1buf, csr 2000 maxp 0200
(queue empty)

ep1out (hw1): 1buf, csr 0000 maxp 0200
req ce3e4f40, !short, 0/51



N900~> dmesg
[41951.144866] musb_hdrc periph: enabled ep1in for bulk IN, maxpacket 512
[41951.144897] musb_hdrc periph: enabled ep1out for bulk OUT, maxpacket 512
[41951.144958] g_file_storage gadget: high speed config #1



The N900 has the PR1.1 firmware update installed and i connect it directly to a USB port of my laptop (tried all ports, no difference) using the original Nokia USB cable.

If you experience problems maybe try the commands above and see if their output is any different for you (even with a windows machine you should be able to run 'dmesg' and 'cat /proc/driver/musb_hdrc' in the X Terminal). If yes, (i would expect it says not " g_file_storage gadget: high speed config #1" in the dmesg output but something else) maybe try these suggestions and see if things improve:

- try with the original Nokia USB cable as well as a non Nokia micro USB cable (if you have one - theoretically there could be some defect in the cable shipped)
- connect the device directly to the computers USB port and don't use a switch in between
- try all available USB ports on your computer (many older machines have only a few USB2.0 and several USB1.1 ports)
- try with a different computer if possible

Additionally it would be possible to load the musb_hdrc module on the N900 with debugging enabled so more info could be obtained, That however would require root access, so I would not recommend that to anyone who does not know what he is doing. If I encounter a speed drop I'll doo that myself and post the output here.



Two things I noticed while doing the checks:
- While being mounted on a compter, the MyDocs directory is empty as it got unmounted in the device itself. I assume this is to keep data intact, but wouldn't it make more sense to have MyDocs just mounted readonly, so no files can be copied there by accident that would later disappear under the remounted MyDocs partition (they would still use space though). Just a thought.

- the laptop dmesg output suggests that there are two mass storage devices exported from the N900, sdb (Scsi Disk b) and sdc. I can mount sdc1 (first partition on the 'disk') which turns out to be the MyDocs folder, but sdc, the second detected 'disc' does not even seem to contain a partition. Has anyone an idea what it is about?

Re: Nokia really screwed the pooch with the USB connection
 

I reported on this in a previous thread (of mine, I think).

I have to turn off the phone to get USB 2.0. Yes, it sems weird, since there's a big black bar that says "USB MODE" on it that you can push, while the phone is on and connected to a USB cable... but - turn off the phone, use it as a dumb storage device, and your 2.0 should be in full effect. You're welcome.

Re: Nokia really screwed the pooch with the USB connection
 

I can't charge via PC cable anymore. I'm using the Nokia supplied cable, and get the "Insufficient Power..." message. Never happened before on either of the two devices I had, but now I can never get a charge. This was why I never liked USB port only charging, preferring the dedicated power cable. I could really use that Nokia charger port now.

I tend to use my N900 as a portable drive for samples in the studio, and the constant access is a power drain that is never satisfied, and I'm constantly unplugging from the PC to connect to a charger.

Is no solution or cause known?