[geloest] Wie XBMC / yaVDR mit Android Handy über USB verbinden

ctvdrnoob · 4. Februar 2012

Hallo,
ich möchte mein Android Handy über USB an den yaVDR verbinden.
Ich habe die Option USB Debugging im Android eingeschaltet.
Über den mount Befehl wird mir keine auf das Android hinweisende Info angezeigt.
MTP Tools habe ich auch installiert. Auch damit funktioniert es nicht.

Kann mir jemand weiterhelfen, wie das einzurichten ist? Über Kies_Air funktioniert es übrigens. Ich möchte aber per USB verbinden, um mir die Fotos/Videos auf dem Handy direkt am TV anzeigen zu lassen.

seahawk1986 · 4. Februar 2012

Was sagt denn dmesg nach dem Anstecken?

ctvdrnoob · 4. Februar 2012

Anbei die dmesg-Meldungen:

Code

[    5.218605] EXT4-fs (sda1): ext4_orphan_cleanup: deleting unreferenced inode 287108
[    5.218686] EXT4-fs (sda1): 1 orphan inode deleted
[    5.218688] EXT4-fs (sda1): recovery complete
[    5.386271] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
[    5.910882] scsi 6:0:0:0: Direct-Access     Android    UMS Composite    00 PQ: 0 ANSI: 2
[    5.911371] scsi 6:0:0:1: Direct-Access     Android    UMS Composite    00 PQ: 0 ANSI: 2
[    5.911916] sd 6:0:0:0: Attached scsi generic sg2 type 0
[    5.912068] sd 6:0:0:1: Attached scsi generic sg3 type 0
[    5.916484] sd 6:0:0:0: [sdb] Attached SCSI removable disk
[    5.917109] sd 6:0:0:1: [sdc] Attached SCSI removable disk
[   12.990651] <30>udev[360]: starting version 167
[   13.041958] lp: driver loaded but no devices found
[   13.302047] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro
[   13.330527] MCE: In-kernel MCE decoding enabled.
[   13.336102] EDAC MC: Ver: 2.1.0 Nov 28 2011
[   13.356151] k8temp 0000:00:18.3: Temperature readouts might be wrong - check erratum #141
[   13.371617] i2c i2c-0: nForce2 SMBus adapter at 0x1c00
[   13.371654] i2c i2c-1: nForce2 SMBus adapter at 0x1c40
[   13.420426] EDAC amd64_edac: v3.3.0
[   13.424480] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
[   13.436744] EDAC amd64: DRAM ECC disabled.
[   13.436755] EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load.
[   13.436757]  Either enable ECC checking or force module loading by setting 'ecc_enable_override'.
[   13.436758]  (Note that use of the override may cause unknown side effects.)
[   13.442226] SGI XFS Quota Management subsystem
[   13.478000] XFS mounting filesystem sda6saa7146: register extension 'budget dvb'.
[   13.620573] ACPI: PCI Interrupt Link [APC2] enabled at IRQ 17
[   13.620599] budget dvb 0000:01:07.0: PCI INT A -> Link[APC2] -> GSI 17 (level, low) -> IRQ 17
[   13.620655] saa7146: found saa7146 @ mem ffffc9000034a000 (revision 1, irq 17) (0x13c2,0x101c).
[   13.620662] saa7146 (0): dma buffer size 192512
[   13.620664] DVB: registering new adapter (TT-Budget S2-1600 PCI)
[   13.625277] Ending clean XFS mount for filesystem: sda6
[   13.681001] adapter has MAC addr = 00:d0:5c:cc:a3:39
[   13.733370] input: iMON Panel, Knob and Mouse(15c2:ffdc) as /devices/pci0000:00/0000:00:02.0/usb2/2-7/2-7:1.0/input/input4
[   13.746601] IR NEC protocol handler initialized
[   13.750257] imon 2-7:1.0: 0xffdc iMON LCD, MCE IR (id 0x9f)
[   13.755030] nvidia: module license 'NVIDIA' taints kernel.
[   13.755035] Disabling lock debugging due to kernel taint
[   13.764942] IR RC5(x) protocol handler initialized
[   13.772338] IR RC6 protocol handler initialized
[   13.793317] Registered IR keymap rc-imon-mce
[   13.793523] input: iMON Remote (15c2:ffdc) as /devices/pci0000:00/0000:00:02.0/usb2/2-7/2-7:1.0/rc/rc0/input5
[   13.793620] rc0: iMON Remote (15c2:ffdc) as /devices/pci0000:00/0000:00:02.0/usb2/2-7/2-7:1.0/rc/rc0
[   13.799418] IR JVC protocol handler initialized
[   13.800164] imon 2-7:1.0: iMON device (15c2:ffdc, intf0) on usb<2:3> initialized
[   13.800206] usbcore: registered new interface driver imon
[   13.810474] IR Sony protocol handler initialized
[   13.823321] lirc_dev: IR Remote Control driver registered, major 250
[   13.824785] IR LIRC bridge handler initialized
[   13.863046] cfg80211: Calling CRDA to update world regulatory domain
[   14.166608] stv6110x_attach: Attaching STV6110x
[   14.220632] DVB: registering adapter 0 frontend 0 (STV090x Multistandard)...
[   14.238202] ACPI: PCI Interrupt Link [AAZA] enabled at IRQ 22
[   14.238210] HDA Intel 0000:00:05.0: PCI INT B -> Link[AAZA] -> GSI 22 (level, low) -> IRQ 22
[   14.238213] hda_intel: Disable MSI for Nvidia chipset
[   14.238241] HDA Intel 0000:00:05.0: setting latency timer to 64
[   14.277856] phy0 -> rt2500usb_init_eeprom: Error - Invalid RT chipset detected.
[   14.277862] phy0 -> rt2x00lib_probe_dev: Error - Failed to allocate device.
[   14.277978] usbcore: registered new interface driver rt2500usb
[   14.556159] cfg80211: Updating information on frequency 2412 MHz for a 20 MHz width channel with regulatory rule:
[   14.556164] cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (600 mBi, 2000 mBm)
[   14.556167] cfg80211: Updating information on frequency 2417 MHz for a 20 MHz width channel with regulatory rule:
[   14.556169] cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (600 mBi, 2000 mBm)
[   14.556172] cfg80211: Updating information on frequency 2422 MHz for a 20 MHz width channel with regulatory rule:
[   14.556174] cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (600 mBi, 2000 mBm)
[   14.556176] cfg80211: Updating information on frequency 2427 MHz for a 20 MHz width channel with regulatory rule:
[   14.556179] cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (600 mBi, 2000 mBm)
[   14.556181] cfg80211: Updating information on frequency 2432 MHz for a 20 MHz width channel with regulatory rule:
[   14.556184] cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (600 mBi, 2000 mBm)
[   14.556186] cfg80211: Updating information on frequency 2437 MHz for a 20 MHz width channel with regulatory rule:
[   14.556189] cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (600 mBi, 2000 mBm)
[   14.556191] cfg80211: Updating information on frequency 2442 MHz for a 20 MHz width channel with regulatory rule:
[   14.556193] cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (600 mBi, 2000 mBm)
[   14.556195] cfg80211: Updating information on frequency 2447 MHz for a 20 MHz width channel with regulatory rule:
[   14.556198] cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (600 mBi, 2000 mBm)
[   14.556200] cfg80211: Updating information on frequency 2452 MHz for a 20 MHz width channel with regulatory rule:
[   14.556203] cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (600 mBi, 2000 mBm)
[   14.556205] cfg80211: Updating information on frequency 2457 MHz for a 20 MHz width channel with regulatory rule:
[   14.556208] cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (600 mBi, 2000 mBm)
[   14.556210] cfg80211: Updating information on frequency 2462 MHz for a 20 MHz width channel with regulatory rule:
[   14.556212] cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (600 mBi, 2000 mBm)
[   14.556215] cfg80211: Updating information on frequency 2467 MHz for a 20 MHz width channel with regulatory rule:
[   14.556217] cfg80211: 2457000 KHz - 2482000 KHz @  KHz), (600 mBi, 2000 mBm)
[   14.556219] cfg80211: Updating information on frequency 2472 MHz for a 20 MHz width channel with regulatory rule:
[   14.556222] cfg80211: 2457000 KHz - 2482000 KHz @  KHz), (600 mBi, 2000 mBm)
[   14.556224] cfg80211: Updating information on frequency 2484 MHz for a 20 MHz width channel with regulatory rule:
[   14.556227] cfg80211: 2474000 KHz - 2494000 KHz @  KHz), (600 mBi, 2000 mBm)
[   14.594446] RPC: Registered udp transport module.
[   14.594450] RPC: Registered tcp transport module.
[   14.594452] RPC: Registered tcp NFSv4.1 backchannel transport module.
[   14.680572] cfg80211: Updating information on frequency 2412 MHz for a 20 MHz width channel with regulatory rule:
[   14.680577] cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (300 mBi, 2000 mBm)
[   14.680580] cfg80211: Updating information on frequency 2417 MHz for a 20 MHz width channel with regulatory rule:
[   14.680582] cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (300 mBi, 2000 mBm)
[   14.680585] cfg80211: Updating information on frequency 2422 MHz for a 20 MHz width channel with regulatory rule:
[   14.680587] cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (300 mBi, 2000 mBm)
[   14.680589] cfg80211: Updating information on frequency 2427 MHz for a 20 MHz width channel with regulatory rule:
[   14.680592] cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (300 mBi, 2000 mBm)
[   14.680594] cfg80211: Updating information on frequency 2432 MHz for a 20 MHz width channel with regulatory rule:
[   14.680597] cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (300 mBi, 2000 mBm)
[   14.680599] cfg80211: Updating information on frequency 2437 MHz for a 20 MHz width channel with regulatory rule:
[   14.680601] cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (300 mBi, 2000 mBm)
[   14.680604] cfg80211: Updating information on frequency 2442 MHz for a 20 MHz width channel with regulatory rule:
[   14.680606] cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (300 mBi, 2000 mBm)
[   14.680608] cfg80211: Updating information on frequency 2447 MHz for a 20 MHz width channel with regulatory rule:
[   14.680611] cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (300 mBi, 2000 mBm)
[   14.680613] cfg80211: Updating information on frequency 2452 MHz for a 20 MHz width channel with regulatory rule:
[   14.680616] cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (300 mBi, 2000 mBm)
[   14.680618] cfg80211: Updating information on frequency 2457 MHz for a 20 MHz width channel with regulatory rule:
[   14.680620] cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (300 mBi, 2000 mBm)
[   14.680622] cfg80211: Updating information on frequency 2462 MHz for a 20 MHz width channel with regulatory rule:
[   14.680625] cfg80211: 2402000 KHz - 2472000 KHz @  KHz), (300 mBi, 2000 mBm)
[   14.680627] cfg80211: Updating information on frequency 2467 MHz for a 20 MHz width channel with regulatory rule:
[   14.680630] cfg80211: 2457000 KHz - 2482000 KHz @  KHz), (300 mBi, 2000 mBm)
[   14.680632] cfg80211: Updating information on frequency 2472 MHz for a 20 MHz width channel with regulatory rule:
[   14.680635] cfg80211: 2457000 KHz - 2482000 KHz @  KHz), (300 mBi, 2000 mBm)
[   14.680637] cfg80211: Updating information on frequency 2484 MHz for a 20 MHz width channel with regulatory rule:
[   14.680639] cfg80211: 2474000 KHz - 2494000 KHz @  KHz), (300 mBi, 2000 mBm)
[   14.680642] cfg80211: World regulatory domain updated:
[   14.680644] cfg80211:     (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[   14.680646] cfg80211:     (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[   14.680649] cfg80211:     (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[   14.680651] cfg80211:     (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[   14.680654] cfg80211:     (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[   14.680656] cfg80211:     (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[   14.682270] FS-Cache: Loaded
[   14.698997] cdc_acm 1-6:1.1: This device cannot do calls on its own. It is not a modem.
[   14.699144] cdc_acm 1-6:1.1: ttyACM0: USB ACM device
[   14.700510] usbcore: registered new interface driver cdc_acm
[   14.700514] cdc_acm: v0.26:USB Abstract Control Model driver for USB modems and ISDN adapters
[   14.754709] FS-Cache: Netfs 'nfs' registered for caching
[   14.812928] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[   14.831088] ieee80211 phy1: Selected rate control algorithm 'minstrel_ht'
[   14.832319] Registered led device: rt73usb-phy1::radio
[   14.832390] Registered led device: rt73usb-phy1::assoc
[   14.832464] Registered led device: rt73usb-phy1::quality
[   14.835764] usbcore: registered new interface driver rt73usb
[   15.157549] ACPI: PCI Interrupt Link [APC8] enabled at IRQ 16
[   15.157574] nvidia 0000:02:00.0: PCI INT A -> Link[APC8] -> GSI 16 (level, low) -> IRQ 16
[   15.157584] nvidia 0000:02:00.0: setting latency timer to 64
[   15.157589] vgaarb: device changed decodes: PCI:0000:02:00.0,olddecodes=io+mem,decodes=none:owns=io+mem
[   15.157847] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  270.41.06  Mon Apr 18 14:53:56 PDT 2011
[   15.300415] input: eventlircd as /devices/virtual/input/input6
[   15.410247] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   15.739874] svc: failed to register lockdv1 RPC service (errno 97).
[   15.743593] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
[   15.747702] NFSD: starting 90-second grace period
[   17.336980] wlan0: authenticate with 00:04:0e:53:02:2c (try 1)
[   17.350956] wlan0: authenticated
[   17.408232] wlan0: associate with 00:04:0e:53:02:2c (try 1)
[   17.411760] wlan0: RX AssocResp from 00:04:0e:53:02:2c (capab=0x451 status=0 aid=1)
[   17.411764] wlan0: associated
[   17.423808] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[   17.600051] Intel AES-NI instructions are not detected.
[   20.291526] padlock_aes: VIA PadLock not detected.
[   27.960018] wlan0: no IPv6 routers present
[  402.890882] usb 1-6: USB disconnect, address 4
[  416.440024] usb 1-6: new high speed USB device using ehci_hcd and address 6
[  418.012630] usb 1-6: USB disconnect, address 6
[  418.330027] usb 1-6: new high speed USB device using ehci_hcd and address 7
[  467.736757] usb 1-6: USB disconnect, address 7
[  478.940027] usb 1-6: new high speed USB device using ehci_hcd and address 8
[  479.102294] scsi7 : usb-storage 1-6:1.0
[  479.102765] cdc_acm 1-6:1.1: This device cannot do calls on its own. It is not a modem.
[  479.103039] cdc_acm 1-6:1.1: ttyACM0: USB ACM device
[  480.100881] scsi 7:0:0:0: Direct-Access     Android    UMS Composite    00 PQ: 0 ANSI: 2
[  480.101367] scsi 7:0:0:1: Direct-Access     Android    UMS Composite    00 PQ: 0 ANSI: 2
[  480.101985] sd 7:0:0:0: Attached scsi generic sg2 type 0
[  480.102359] sd 7:0:0:1: Attached scsi generic sg3 type 0
[  480.108907] sd 7:0:0:0: [sdb] Attached SCSI removable disk
[  480.110497] sd 7:0:0:1: [sdc] Attached SCSI removable disk
[ 1148.223760] usb 1-6: USB disconnect, address 8
[ 1232.428446] Bluetooth: Core ver 2.15
[ 1232.428483] NET: Registered protocol family 31
[ 1232.428485] Bluetooth: HCI device and connection manager initialized
[ 1232.428488] Bluetooth: HCI socket layer initialized
[ 1232.436687] Bluetooth: L2CAP ver 2.15
[ 1232.436690] Bluetooth: L2CAP socket layer initialized
[ 1232.443372] Bluetooth: RFCOMM TTY layer initialized
[ 1232.443379] Bluetooth: RFCOMM socket layer initialized
[ 1232.443382] Bluetooth: RFCOMM ver 1.11
[ 2894.780032] usb 1-6: new high speed USB device using ehci_hcd and address 9
[ 2894.934224] scsi8 : usb-storage 1-6:1.0
[ 2894.934679] cdc_acm 1-6:1.1: This device cannot do calls on its own. It is not a modem.
[ 2894.934831] cdc_acm 1-6:1.1: ttyACM0: USB ACM device
[ 2895.930763] scsi 8:0:0:0: Direct-Access     Android    UMS Composite    00 PQ: 0 ANSI: 2
[ 2895.931244] scsi 8:0:0:1: Direct-Access     Android    UMS Composite    00 PQ: 0 ANSI: 2
[ 2895.931950] sd 8:0:0:0: Attached scsi generic sg2 type 0
[ 2895.932311] sd 8:0:0:1: Attached scsi generic sg3 type 0
[ 2895.940377] sd 8:0:0:0: [sdb] Attached SCSI removable disk
[ 2895.941001] sd 8:0:0:1: [sdc] Attached SCSI removable disk
[ 2926.080042] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x180000 action 0x6 frozen
[ 2926.082196] ata2: SError: { 10B8B Dispar }
[ 2926.084405] sr 1:0:0:0: CDB: Get event status notification: 4a 01 00 00 10 00 00 00 08 00
[ 2926.084419] ata2.00: cmd a0/00:00:00:08:00/00:00:00:00:00/a0 tag 0 pio 16392 in
[ 2926.084420]          res 40/00:02:00:08:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
[ 2926.089112] ata2.00: status: { DRDY }
[ 2926.091555] ata2: hard resetting link
[ 2926.091558] ata2: nv: skipping hardreset on occupied port
[ 2931.620022] ata2: link is slow to respond, please be patient (ready=0)
[ 2936.120023] ata2: SRST failed (errno=-16)
[ 2936.122511] ata2: hard resetting link
[ 2936.122515] ata2: nv: skipping hardreset on occupied port
[ 2941.650023] ata2: link is slow to respond, please be patient (ready=0)
[ 2946.150025] ata2: SRST failed (errno=-16)
[ 2946.152575] ata2: hard resetting link
[ 2946.152578] ata2: nv: skipping hardreset on occupied port
[ 2951.680070] ata2: link is slow to respond, please be patient (ready=0)
[ 2981.200027] ata2: SRST failed (errno=-16)
[ 2981.200096] ata2: limiting SATA link speed to 1.5 Gbps
[ 2981.200101] ata2: hard resetting link
[ 2981.200104] ata2: nv: skipping hardreset on occupied port
[ 2986.250022] ata2: SRST failed (errno=-16)
[ 2986.250096] ata2: reset failed, giving up
[ 2986.253216] ata2.00: disabled
[ 2986.253242] ata2: EH complete
[ 4646.932132] usb 1-6: USB disconnect, address 9
[ 4648.101881] usb 2-5: USB disconnect, address 2
[ 4656.900027] usb 2-2: new low speed USB device using ohci_hcd and address 4
[ 4657.200382] input: MLK wireless keyboard and mouse as /devices/pci0000:00/0000:00:02.0/usb2/2-2/2-2:1.0/input/input7
[ 4657.200509] sunplus 0003:04FC:05D8.0003: input,hidraw0: USB HID v1.00 Keyboard [MLK wireless keyboard and mouse] on usb-0000:00:02.0-2/input0
[ 4657.212082] sunplus 0003:04FC:05D8.0004: fixing up Sunplus Wireless Desktop report descriptor
[ 4657.213341] input: MLK wireless keyboard and mouse as /devices/pci0000:00/0000:00:02.0/usb2/2-2/2-2:1.1/input/input8
[ 4657.213579] sunplus 0003:04FC:05D8.0004: input,hiddev0,hidraw1: USB HID v1.00 Mouse [MLK wireless keyboard and mouse] on usb-0000:00:02.0-2/input1
[13286.140030] usb 1-5: new high speed USB device using ehci_hcd and address 11
[13286.291843] scsi9 : usb-storage 1-5:1.0
[13286.292287] cdc_acm 1-5:1.1: This device cannot do calls on its own. It is not a modem.
[13286.292435] cdc_acm 1-5:1.1: ttyACM0: USB ACM device
[13287.291010] scsi 9:0:0:0: Direct-Access     Android    UMS Composite    00 PQ: 0 ANSI: 2
[13287.291492] scsi 9:0:0:1: Direct-Access     Android    UMS Composite    00 PQ: 0 ANSI: 2
[13287.292102] sd 9:0:0:0: Attached scsi generic sg2 type 0
[13287.292498] sd 9:0:0:1: Attached scsi generic sg3 type 0
[13287.296945] sd 9:0:0:0: [sdb] Attached SCSI removable disk
[13287.303633] sd 9:0:0:1: [sdc] Attached SCSI removable disk

Alles anzeigen

ctvdrnoob · 11. Februar 2012

wie macht ihr das mit dem Verbinden des Android Handys mit yavdr/xbmc?

fatzgenfatz · 11. Februar 2012

Hallo,

wie wird denn dein Handy am PC erkannt? Als Massenspeichergerät oder nur als MTP-Gerät?
Nach dem Anstecken muss ich auf meinem Nexus S noch den USB-Massenspeicher aktivieren (da kommt eine Notification), damit auf meinem PC der Speicher als Laufwerk erkannt wird.
Alternativ kannst du auch eine App probieren, die die Medieninhalte deines Telefons als DLNA-Speicher verteilt (Twonky mobile oder iMediaShare z.B.).

Welche Android-Version verwendest du?

mfG,
f.

ctvdrnoob · 11. Februar 2012

Das Handy wird gar nicht erkannt.
Wenn ich auf Massenspeicher umschalte, kommt die Meldung mit Trennen des USB-Kabels. Das bringt aber auch keine Änderung.
Am Windows XP Rechner funktioniert alles problemlos.
Android 2.3.4 Gingerbread wird verwendet.

fatzgenfatz · 11. Februar 2012

Schau mal unter http://www.google.com/help/hc/…UsersGuide-2.3-103-de.pdf
Dort (auf Seite 73) findest du die Vorgehensweise zum Verbinden mit einem PC.
Bei mir funktioniert das einwandfrei.

mfG,
f.

ctvdrnoob · 11. Februar 2012

Ich habe Handy und yavdr per USB-Kabel verbunden. Es wird folgendes angezeigt auf yavdr in der Konsole:

Code

mount
/dev/sda1 on / type ext4 (rw,errors=remount-ro)
proc on /proc type proc (rw,noexec,nosuid,nodev)
none on /sys type sysfs (rw,noexec,nosuid,nodev)
fusectl on /sys/fs/fuse/connections type fusectl (rw)
none on /sys/kernel/debug type debugfs (rw)
none on /sys/kernel/security type securityfs (rw)
none on /dev type devtmpfs (rw,mode=0755)
none on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
none on /dev/shm type tmpfs (rw,nosuid,nodev)
none on /var/run type tmpfs (rw,nosuid,mode=0755)
none on /var/lock type tmpfs (rw,noexec,nosuid,nodev)
/dev/sda6 on /media type xfs (rw)
rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
/media/video.00 on /srv/share/vdr type none (rw,bind)
nfsd on /proc/fs/nfsd type nfsd (rw)

Alles anzeigen

Auf dem Handy unter Einstellungen/USB-Massenspeicher/USB verbinden wird angezeigt, daß per USB verbunden ist.

Syslog:

Code

Feb 11 11:26:52 VDR1 kernel: [ 7789.036508] usb 1-6: USB disconnect, address 9
Feb 11 11:26:55 VDR1 kernel: [ 7792.400030] usb 1-6: new high speed USB device using ehci_hcd and address 10
Feb 11 11:26:55 VDR1 kernel: [ 7792.551703] scsi9 : usb-storage 1-6:1.0
Feb 11 11:26:55 VDR1 kernel: [ 7792.552010] cdc_acm 1-6:1.1: This device cannot do calls on its own. It is not a modem.
Feb 11 11:26:55 VDR1 kernel: [ 7792.553748] cdc_acm 1-6:1.1: ttyACM0: USB ACM device
Feb 11 11:26:56 VDR1 kernel: [ 7793.550888] scsi 9:0:0:0: Direct-Access     Android    UMS Composite    00 PQ: 0 ANSI: 2
Feb 11 11:26:56 VDR1 kernel: [ 7793.552620] scsi 9:0:0:1: Direct-Access     Android    UMS Composite    00 PQ: 0 ANSI: 2
Feb 11 11:26:56 VDR1 kernel: [ 7793.553387] sd 9:0:0:0: Attached scsi generic sg2 type 0
Feb 11 11:26:56 VDR1 kernel: [ 7793.553728] sd 9:0:0:1: Attached scsi generic sg3 type 0
Feb 11 11:26:56 VDR1 kernel: [ 7793.558763] sd 9:0:0:0: [sdb] Attached SCSI removable disk
Feb 11 11:26:56 VDR1 kernel: [ 7793.562010] sd 9:0:0:1: [sdc] Attached SCSI removable disk

Alles anzeigen

fatzgenfatz · 11. Februar 2012

Bei mir sieht das so aus:
Nach Anstecken des Telefons:

Code

[62176.336079] usb 2-2: new high speed USB device number 10 using ehci_hcd
[62176.471179] scsi10 : usb-storage 2-2:1.0
[62177.468950] scsi 10:0:0:0: Direct-Access     Google   File-CD Gadget   0000 PQ: 0 ANSI: 2
[62177.504685] sd 10:0:0:0: Attached scsi generic sg8 type 0
[62177.510520] sd 10:0:0:0: [sdg] Attached SCSI removable disk

Nachdem ich auf "USB-Speicher aktivieren" am Telefon gedrückt habe:

Code

[62176.336079] usb 2-2: new high speed USB device number 10 using ehci_hcd
[62176.471179] scsi10 : usb-storage 2-2:1.0
[62177.468950] scsi 10:0:0:0: Direct-Access     Google   File-CD Gadget   0000 PQ: 0 ANSI: 2
[62177.504685] sd 10:0:0:0: Attached scsi generic sg8 type 0
[62177.510520] sd 10:0:0:0: [sdg] Attached SCSI removable disk
[62298.004463] sd 10:0:0:0: [sdg] 27957215 512-byte logical blocks: (14.3 GB/13.3 GiB)
[62298.005478] sd 10:0:0:0: [sdg] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[62298.010741]  sdg:




mount:
/dev/sdg on /media/35EE-1E0E type vfat (rw,nosuid,nodev,uid=1000,gid=1000,shortname=mixed,dmask=0077,utf8=1,showexec,flush,uhelper=udisks)

Alles anzeigen

Versuch mal eine udev-Regel für das Telefon zu erstellen.
Dazu findest du zuerst mittels lsusb die Vendor-ID des Telefons raus:

Code

lsusb
Bus 002 Device 010: ID 18d1:4e22 Google Inc. Nexus S (debug)

Die Vendor-ID ist in diesem Fall "18d1".

Anschließend erstellst du dir in /etc/udev/rules.d/ eine Datei namens "99-android.rules" (kann auch anders heissen, ich glaube nur das ".rules" ist wichtig.
In die Datei schreibst du:

Code

SUBSYSTEM==usb, SYSFS{idVendor}==18d1, MODE=0666

Hier musst du die Vendor-ID (18d1) durch deine Vendor-ID ersetzen.
Anschließend musst du udev neu starten (reboot geht auch).

Vielleicht hilft das ja.

mfG,
f.

ctvdrnoob · 11. Februar 2012

Hat leider nicht geholfen.
Hier meine Aktionen:

Code

lsusb
Bus 002 Device 003: ID 15c2:ffdc SoundGraph Inc. iMON PAD Remote Controller
Bus 002 Device 002: ID 04fc:05d8 Sunplus Technology Co., Ltd Wireless keyboard/mouse
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 006: ID 04e8:685e Samsung Electronics Co., Ltd
Bus 001 Device 002: ID 148f:2573 Ralink Technology, Corp. RT2501/RT2573 Wireless Adapter
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


/etc/udev/rules.d$ sudo vi 99-android.rules
SUBSYSTEM==usb, SYSFS{idVendor}==04e8, MODE=0666


sudo reboot


/proc/scsi/scsi
Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
  Vendor: ATA      Model: ST3320620AS      Rev: 3.AA
  Type:   Direct-Access                    ANSI  SCSI revision: 05
Host: scsi1 Channel: 00 Id: 00 Lun: 00
  Vendor: HL-DT-ST Model: DVDRAM GH20NS10  Rev: EL00
  Type:   CD-ROM                           ANSI  SCSI revision: 05
Host: scsi7 Channel: 00 Id: 00 Lun: 00
  Vendor: Android  Model:   UMS Composite  Rev:   00
  Type:   Direct-Access                    ANSI  SCSI revision: 02
Host: scsi7 Channel: 00 Id: 00 Lun: 01
  Vendor: Android  Model:   UMS Composite  Rev:   00
  Type:   Direct-Access                    ANSI  SCSI revision: 02


sudo mount /dev/sdb /media/android
umount: /dev/sdb: unbekanntes Gerät

Alles anzeigen

schnoefftel · 11. Februar 2012

Zitat

Ich habe die Option USB Debugging im Android eingeschaltet.

Muss das nicht abgeschaltet sein?
Wird Dein Handy so noch unter Windows erkannt?
Versuch mal das debugging wieder abzuschalten, dann auf dem Androiden unter Einstellungen, Drahtlos und Netzwerk, USB- Einstellungen, auf Massenspeicher einstellen. Geht nur, wenn das Gerät nicht verbunden ist.

Gruß Jan

ctvdrnoob · 11. Februar 2012

Ich hab es hinbekommen.
Wenn am oberen Bildschirmrand des Handys das USB Symbol angezeigt wird, muß man die Leiste nach unten ziehen. Dann wird der Punkt USB-Verbindung sichtbar --> antippen --> Bildschirm mit grünem Android-Männchen erscheint --> Massenspeicher verbinden wählen --> hat sich dann verbunden.
Anschließend noch auf dem VDR mounten (sudo mount /dev/sdb /media/android) und dann kann man auf die Verzeichnisse zugreifen.

fatzgenfatz · 11. Februar 2012

Zitat von ctvdrnoob

Ich hab es hinbekommen.
Wenn am oberen Bildschirmrand des Handys das USB Symbol angezeigt wird, muß man die Leiste nach unten ziehen. Dann wird der Punkt USB-Verbindung sichtbar --> antippen --> Bildschirm mit grünem Android-Männchen erscheint --> Massenspeicher verbinden wählen --> hat sich dann verbunden.

Huch, du hast es also genau so gemacht, wie es in der Anleitung steht, und auf einmal funktioniert es? Mit so was konnte nun wirklich niemand rechnen!

SCNR
f.

ctvdrnoob · 11. Februar 2012

wer (konzentriert) lesen kann, ist klar im Vorteil
Ich war bei USB-Verbindung in den Einstellungen und nicht in der Statusleiste.

Vielen Dank, das Handbuch kannte ich auch noch nicht.

[geloest] Wie XBMC / yaVDR mit Android Handy über USB verbinden

Jetzt mitmachen!

Teilen

Benutzer online in diesem Thema