[Q] archos detects my canon powershot camera but doesn't show the pictures - Gen8, Gen9, Gen10 Q&A, Help & Troubleshooting

Hi,
When I plug my canon powershot camera into the archos 101 usb, it recognises my camera (message "external camera connected" or something like that) but when I look into the folder, it's empty... it doesn't show my pictures stored on the camera's sd card
anybody any ideas?
external hd drives, mouse, usb sticks etc all work fine
Cheers
B

berre said:
When I plug my canon powershot camera into the archos 101 usb, it recognises my camera (message "external camera connected" or something like that) but when I look into the folder, it's empty... it doesn't show my pictures stored on the camera's sd card
Click to expand...
Click to collapse
Most camera's have a setting to change the usb mode from PTP to USB STORAGE. Have you tried to change that?

I've went through the menu's of my camera but doesn't look like it has this setting...
cheers
B

berre said:
I've went through the menu's of my camera but doesn't look like it has this setting...
Click to expand...
Click to collapse
When You connect your camera to a computer what OS is the computer running?
How is the SD card in your camera formatted?

Are the photos take in RAW format and not JPG??? Your archos won't be able to view RAW, which is a shame...

OS is XP, pictures are jpeg format.
I'll see if I can find out how the SD is formatted tonight.
cheers
b

file system of the SD card is FAT
I've tried connecting a USB card reader to read the SD card but I get the same behaviour as when I try to connect my phone
see topic http://forum.xda-developers.com/showthread.php?t=1123491
so I'm kinda stuck on getting the images on my archos 101... a person in the other topic suggested installing urukdroid, would this help?
cheers
B

I have the same problem. It worked fine before, then one day I connected it and it wasn't working. Didn't change anything on the camera.

It is sadly a known problem with the 101 that the USB breaks.
The only chance you have is to RMA the device

fzelle said:
It is sadly a known problem with the 101 that the USB breaks.
The only chance you have is to RMA the device
Click to expand...
Click to collapse
There's nothing in this thread that says hardware failure. Why would you say the only choice is to RMA it?
berre: You should do some testing mate. Install OSMonitor and use it to watch the dmesg output when you plug in the usb devices. Test a few USB Flash Drives, wireless mice, etc. As I've said, I certainly have trouble with some USB devices, but it's not an RMA situation.
As for getting the pictures on your 101, copy them to your PC, then copy over wifi, or connect the A101 to your PC, or use a microSD card in your camera with a microsd adapter, then you can just put it straight into the 101. Or move them to a usb flash drive if you can find a working one.

this is my alogcat
seems like it's discovering my camera (detects that it's a canon) but there's an error message "Parameter 'INTERFACE' not found"
anybody any idea what this means?
D/dalvikvm(12735): GC_FOR_MALLOC freed 3809 objects / 173920 bytes in 115ms
W/InputManagerService( 1319): Window already focused, ignoring focus gain of: [email protected]
D/WifiService( 1319): ACTION_BATTERY_CHANGED pluggedType: 0
D/SiMiClock( 1717): onUpdate
I/cat ( 1174): <7>usb usb2: usb resume
I/cat ( 1174): <7>hub 2-0:1.0: hub_resume
I/cat ( 1174): <7>hub 2-0:1.0: port 1: status 0101 change 0001
I/cat ( 1174): <7>hub 2-0:1.0: state 7 ports 1 chg 0002 evt 0000
I/cat ( 1174): <7>hub 2-0:1.0: port 1, status 0101, change 0000, 12 Mb/s
I/cat ( 1174): <6>usb 2-1: new high speed USB device using musb_hdrc and address 4
I/cat ( 1174): <7>usb 2-1: default language 0x0409
I/cat ( 1174): <6>usb 2-1: New USB device found, idVendor=04a9, idProduct=30fc
I/cat ( 1174): <6>usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
I/cat ( 1174): <6>usb 2-1: Product: Canon Digital Camera
I/cat ( 1174): <6>usb 2-1: Manufacturer: Canon Inc.
E/NetlinkEvent( 1223): NetlinkEvent::FindParam(): Parameter 'INTERFACE' not found
I/Vold ( 1223): handleUsbEvent(): Missing property, ignoring event
I/cat ( 1174): <7>usb 2-1: uevent
I/cat ( 1174): <7>usb 2-1: usb_probe_device
I/cat ( 1174): <6>usb 2-1: configuration #1 chosen from 1 choice
I/cat ( 1174): <7>usb 2-1: adding 2-1:1.0 (config #1, interface 0)
I/cat ( 1174): <7>usb 2-1:1.0: uevent
I/Vold ( 1223): Starting gphotofs
I/StorageNotification( 1319): Media {/mnt/storage/extcamera} state changed from {unmounted} -> {mounted}
W/StorageNotification( 1319): setMediaStorageNotification type=4 icon=17302220 visible=true
D/MediaScannerReceiver( 4966): Just got intent Intent { act=android.intent.action.MEDIA_MOUNTED dat=file:///mnt/storage/extcamera cmp=com.android.providers.media/.MediaScannerReceiver (has extras) }
I/BootReceiver( 6648): Got intent with action android.intent.action.MEDIA_MOUNTED
I/cat ( 1174): <7>/mnt/flash/releases/G8A/v2.3.25-r85838/arcbuild/linux/drivers/usb/core/inode.c: creating file '004'
I/cat ( 1174): <7>hub 2-0:1.0: state 7 ports 1 chg 0000 evt 0002
I/cat ( 1174): <7>hub 2-0:1.0: port 1 enable change, status 00000503
D/AosUpdate:MediaMountReceiver(12628): android.intent.action.MEDIA_MOUNTED / file:///mnt/storage/extcamera
D/dalvikvm(28664): GC_EXPLICIT freed 17329 objects / 1063424 bytes in 77ms
D/WifiService( 1319): ACTION_BATTERY_CHANGED pluggedType: 0
D/SiMiClock( 1717): onUpdate
I/ActivityManager( 1319): Starting activity: Intent { act=archos.intent.action.FILE_MANAGER dat=file:///mnt/storage/extcamera flg=0x10000000 cmp=com.archos.fm/.FileManager bnds=[0,58][980,122] }
V/alogcat (12735): save instance
V/alogcat (12735): paused
D/FileManager(12638): onResume: register the ActivityBackgroundResizer
D/ActivityBackgroundResizer(12638): onGlobalLayout
D/ActivityBackgroundResizer(12638): onGLobalLayout: 980x600
D/ActivityBackgroundResizer(12638): onGlobalLayout: no resizing required (980x600)
I/ActivityManager( 1319): Displayed activity com.archos.fm/.FileManager: 533 ms (total 533 ms)
D/alogcat (12735): stopping ...
D/alogcat (12735): stopped
W/KeyCharacterMap(12638): No keyboard for id -1
W/KeyCharacterMap(12638): Using default keymap: /system/usr/keychars/qwerty.kcm.bin
D/dalvikvm(12638): GC_EXTERNAL_ALLOC freed 3643 objects / 184896 bytes in 74ms
D/dalvikvm(12638): GC_EXTERNAL_ALLOC freed 678 objects / 38768 bytes in 55ms
D/dalvikvm(12638): GC_EXTERNAL_ALLOC freed 7 objects / 232 bytes in 27ms
D/dalvikvm(12638): GC_EXTERNAL_ALLOC freed 7 objects / 216 bytes in 27ms
D/dalvikvm(12638): GC_EXTERNAL_ALLOC freed 8 objects / 264 bytes in 27ms
D/dalvikvm(12638): GC_EXTERNAL_ALLOC freed 196 objects / 7064 bytes in 27ms
W/KeyCharacterMap(12638): No keyboard for id -1
W/KeyCharacterMap(12638): Using default keymap: /system/usr/keychars/qwerty.kcm.bin
D/alogcat (12735): stopping ...
D/alogcat (12735): canceling periodic saves
V/alogcat (12735): started
V/alogcat (12735): resumed
D/alogcat (12735): starting ...
W/IInputConnectionWrapper(12638): showStatusIcon on inactive InputConnection
D/dalvikvm(31530): GC_FOR_MALLOC freed 310 objects / 443984 bytes in 124ms
D/dalvikvm(31530): GC_FOR_MALLOC freed 222 objects / 439856 bytes in 75ms
D/SiMiClock( 1717): onUpdate
D/dalvikvm(31530): GC_FOR_MALLOC freed 167 objects / 435048 bytes in 38ms
D/dalvikvm(31530): GC_FOR_MALLOC freed 73 objects / 430536 bytes in 76ms
D/dalvikvm(31530): GC_FOR_MALLOC freed 70 objects / 430424 bytes in 77ms
I/cat ( 1174): <7>hub 2-0:1.0: state 7 ports 1 chg 0000 evt 0002
I/cat ( 1174): <7>hub 2-0:1.0: port 1, status 0100, change 0001, 12 Mb/s
I/cat ( 1174): <6>usb 2-1: USB disconnect, address 4
I/cat ( 1174): <7>usb 2-1: unregistering device
I/cat ( 1174): <7>usb 2-1: usb_disable_device nuking all URBs
I/cat ( 1174): <7>usb 2-1: unregistering interface 2-1:1.0
I/Vold ( 1223): Stopping gphotofs
I/cat ( 1174): <7>usb 2-1:1.0: uevent
I/StorageNotification( 1319): Media {/mnt/storage/extcamera} state changed from {mounted} -> {unmounted}
D/VoldCmdListener( 1223): volume shared /mnt/storage ums
W/StorageNotification( 1319): setMediaStorageNotification type=4 icon=0 visible=false
D/MediaScannerReceiver( 4966): Just got intent Intent { act=android.intent.action.MEDIA_EJECT dat=file:///mnt/storage/extcamera cmp=com.android.providers.media/.MediaScannerReceiver }
E/NetlinkEvent( 1223): NetlinkEvent::FindParam(): Parameter 'INTERFACE' not found
I/Vold ( 1223): handleUsbEvent(): Missing property, ignoring event
I/cat ( 1174): <7>usb 2-1: uevent
I/BootReceiver( 6648): Got intent with action android.intent.action.MEDIA_EJECT
I/logwrapper(12750): /usr/bin/gphotofs terminated by exit(1)
I/cat ( 1174): <7>hub 2-0:1.0: debounce: port 1: total 100ms stable 100ms status 0x100
I/cat ( 1174): <3>init: untracked pid 12770 exited
I/cat ( 1174): <7>hub 2-0:1.0: hub_suspend
I/cat ( 1174): <7>usb usb2: bus auto-suspend
D/dalvikvm( 4966): GC_EXPLICIT freed 1213 objects / 61504 bytes in 91ms
D/dalvikvm( 6648): GC_EXPLICIT freed 201 objects / 11520 bytes in 73ms
W/KeyCharacterMap(12735): No keyboard for id -1
W/KeyCharacterMap(12735): Using default keymap: /system/usr/keychars/qwerty.kcm.bin

The (1223) shows that message is actually a different process, so I don't think that's related. Look at this line though:
/StorageNotification( 1319): Media {/mnt/storage/extcamera} state changed from {unmounted} -> {mounted}
Notice it says /mnt/storage/extcamera? And "state changed from unmounted to mounted"? Have you looked in that directory? I bet your pics are there.

nope, I think I checked that yesterday and folder was empty... I'll double-check tonight but unless there's a second extcamera folder, it was empty
cheers
b

confirmed, that directory is empty as well.
brgds
b

Maybe i'm wrong, but i think that this isn't the pictures folder, but the access to the camera, maybe Android want to use your camera as a camera (and not as a storage)
I don't really know, but, with my little linux knowledge i think that it's possible.
(In Linux everything is a file, even the hardware)

eagleofdeath13 said:
Maybe i'm wrong, but i think that this isn't the pictures folder, but the access to the camera, maybe Android want to use your camera as a camera (and not as a storage)
I don't really know, but, with my little linux knowledge i think that it's possible.
(In Linux everything is a file, even the hardware)
Click to expand...
Click to collapse
Everything is possible in Linux, but in this case, the mount is being handled by gphotofs, which is a PTP camera storage driver. It's supposed to mount PTP cameras as R/W filesystems, allowing you to access the stored photos. It's independently developed though, so I'm not sure where it got built in.
Gphotofs does not fully support Canon cameras, supposedly Canon locked their PTP to read only, and it's looks like development stopped in 2008, but it seems like it should still show the files though.
I know it's a big step, but I'd try Urukdroid. I don't have a Canon around to test with, but I'd be interested to see what happens. The 1.0 easy install can be done and set up in less than 10 minutes, with no linux or even windows knowledge needed.
One question though. In the log it shows the camera being disconnected and then gphotofs unmounts it. Does this happen immediately after mounting, or did you unplug the usb? If the log shows "/StorageNotification( 1319): Media {/mnt/storage/extcamera} state changed from {mounted} -> {unmounted}" before you actually disconnect the camera, then at least I know why the extcamera directory is empty. That would just leave overamping and canon PTP incompatibilty as the prime suspects.

msticninja said:
One question though. In the log it shows the camera being disconnected and then gphotofs unmounts it. Does this happen immediately after mounting, or did you unplug the usb? If the log shows "/StorageNotification( 1319): Media {/mnt/storage/extcamera} state changed from {mounted} -> {unmounted}" before you actually disconnect the camera, then at least I know why the extcamera directory is empty. That would just leave overamping and canon PTP incompatibilty as the prime suspects.
Click to expand...
Click to collapse
I unplugged the usb so that's normal... first I'm gonna try another usb sd card reader as workaround
I'm not scared of urukdroid but a bit reluctant to void my warranty, especially seen the USB issue which seems to be quite common. I also want to see what the new firmware is all about (next week?)
But I think I might be going for urukdroid anyways as my storage for apps is running out
cheers
B

berre said:
I unplugged the usb so that's normal... first I'm gonna try another usb sd card reader as workaround
I'm not scared of urukdroid but a bit reluctant to void my warranty, especially seen the USB issue which seems to be quite common. I also want to see what the new firmware is all about (next week?)
But I think I might be going for urukdroid anyways as my storage for apps is running out
cheers
B
Click to expand...
Click to collapse
Hmm, I wonder about gphotofs then. If I get some time I'll research it. As far as Uruk, Archos trolls the forums. They've seen our firmware, and they can't really make a case for it doing any real damage. If you have to send it back for replacement, just reflash the original firmware. They don't bother asking, and so far everybody I know with the "SDE Watermark" has gotten a replacement without issue.

Related

Mounting HTC heo on linux

Hello!
How do i mount my HTC hero on ubuntu?
I have tried everything i know about.
Here's some info about it!
It's connected to the machine now.
Code:
[email protected]:~# dmesg|tail
[167350.745833] VFS: Can't find a valid FAT filesystem on dev sda2.
[167350.746019] qnx4: wrong fsid in superblock.
[167392.539945] FAT: bogus number of reserved sectors
[167392.539952] VFS: Can't find a valid FAT filesystem on dev loop0.
[167392.540057] qnx4: wrong fsid in superblock.
[167429.744606] attempt to access beyond end of device
[167429.744614] loop0: rw=0, want=4, limit=2
[167429.744619] EXT3-fs: unable to read superblock
[167584.269145] FAT: bogus number of reserved sectors
[167584.269154] VFS: Can't find a valid FAT filesystem on dev loop0.
[email protected]:~# sfdisk -l
Disk /dev/sda: 19457 cylinders, 255 heads, 63 sectors/track
Warning: extended partition does not start at a cylinder boundary.
DOS and Linux will interpret the contents differently.
Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0
Device Boot Start End #cyls #blocks Id System
/dev/sda1 0 - 0 0 0 Empty
/dev/sda2 * 0+ 18768- 18769- 150759362 f W95 Ext'd (LBA)
/dev/sda3 18768+ 19457- 689- 5529600 8e Linux LVM
/dev/sda4 0 - 0 0 0 Empty
/dev/sda5 3916+ 18768- 14853- 119300096 7 HPFS/NTFS
/dev/sda6 0+ 3915 3916- 31455207 83 Linux
[email protected]:~# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda6 30G 3.3G 25G 12% /
udev 438M 276K 438M 1% /dev
none 438M 0 438M 0% /dev/shm
none 438M 200K 438M 1% /var/run
none 438M 0 438M 0% /var/lock
none 438M 0 438M 0% /lib/init/rw
/dev/sda5 114G 30G 85G 26% /mnt/sda5
/dev/sda6 30G 3.3G 25G 12% /mnt/sda6
[email protected]:~#
First, you should have your data partition of your SD card formatted as FAT32.
Then connect your Hero to your PC using original USB table (you can use non-original, but not everyone of them works).
You should see notification on hero about connected USB, click on this notification and Hero will ask you if you want to connect it as storage device.
Linux should now recognize your Hero as standard USB flash drive.
This works for me.
hELLO!
How can i format my data-partition on my SD-card to FAT32?
And when i connect the hero to the machine, there is no notification on the notification bar!
sorry for bad english.
Broken USB
Hmm, it seems you have some trouble with USB since Hero does not recognize it. My dmesg looks like this, when I connect my Hero (but before I enable it as storage device):
Code:
[47693.001261] usb 6-2: new full speed USB device using uhci_hcd and address 2
[47693.130013] usb 6-2: device descriptor read/64, error -71
[47693.370011] usb 6-2: device descriptor read/64, error -71
[47693.600011] usb 6-2: new full speed USB device using uhci_hcd and address 3
[47693.730011] usb 6-2: device descriptor read/64, error -71
[47693.971260] usb 6-2: device descriptor read/64, error -71
[47694.201263] usb 6-2: new full speed USB device using uhci_hcd and address 4
[47694.621263] usb 6-2: device not accepting address 4, error -71
[47694.680042] hub 6-0:1.0: unable to enumerate USB device on port 2
[47694.961263] usb 2-4: new high speed USB device using ehci_hcd and address 3
[47695.123330] usb 2-4: configuration #1 chosen from 1 choice
[47695.526904] Initializing USB Mass Storage driver...
[47695.527144] scsi6 : SCSI emulation for USB Mass Storage devices
[47695.527234] usb-storage: device found at 3
[47695.527236] usb-storage: waiting for device to settle before scanning
[47695.527250] usbcore: registered new interface driver usb-storage
[47695.527253] USB Mass Storage support registered.
[47700.521271] usb-storage: device scan complete
[47700.523257] scsi 6:0:0:0: Direct-Access HTC Android Phone 0100 PQ: 0 ANSI: 2
[47700.523603] sd 6:0:0:0: Attached scsi generic sg3 type 0
[47700.533243] sd 6:0:0:0: [sdc] Attached SCSI removable disk
i'd try repartitioning the card, looks like a corrupted filesystem.
I don't think repartitioning will help here. /dev/sda is the disk in his computer, because /dev/sda6 is mounted as /. The dmesg output doesn't say anything about /dev/sdb, and there is not even anything about trying to connect a USB device.
My guess is either the cable is bad, or the USB socket on the computer is not connected.
Hi,
I get the same - in Windows it comes up as an unregognised device, and in linux i get
[ 1724.760062] usb 7-1: new full speed USB device using uhci_hcd and address 18
[ 1724.890058] usb 7-1: device descriptor read/64, error -71
[ 1725.130036] usb 7-1: device descriptor read/64, error -71
[ 1725.360077] usb 7-1: new full speed USB device using uhci_hcd and address 19
[ 1725.492549] usb 7-1: device descriptor read/64, error -71
[ 1725.730242] usb 7-1: device descriptor read/64, error -71
[ 1725.960394] usb 7-1: new full speed USB device using uhci_hcd and address 20
[ 1726.380063] usb 7-1: device not accepting address 20, error -71
[ 1726.500053] usb 7-1: new full speed USB device using uhci_hcd and address 21
[ 1726.920281] usb 7-1: device not accepting address 21, error -71
[ 1726.920302] hub 7-0:1.0: unable to enumerate USB device on port 1
and no option on the Hero to mount the partition. I'm open to suggestions
Try another cable and/or another USB port. E.g. the USB ports at the back of your PC are directly soldered to the mainboard, without a shoddy connector and cable in between.

Help ! No USB Connection, ADB. But fastboot works

Hi @all,
maybe some of you guys could help me with my problem.
I updated my Hero to the Cronos 1.4 (I think) a month ago.
Last week, I recognized that the USB mass storage connection does not work anymore.
I tried it on another PC, but no connection.
I tried another Hero with my PC, usb connection worked.
I found this link to the modaco forum:
http://android.modaco.com/content-page/299174/no-adb-no-sd/page/80/
So I followed the instructions of the first post on page 5.
Everything worked till that point where I should flash the RUU_Hero_HTC_WWE_1.76.405.1_R3_WWE_release_signed_NoDriver.exe.
So, here is what I have done so far:
- created a goldcard (with another hero, a friend has one).
- extracted the rom.zip from HTC Hero RUU_Hero_HTC_WWE_2.73.405.5_WWE_release_signed_NoDriver.exe
- flashed it via fastboot
- then I wanted to try the fastboot oem eraseconfig, but like it's said in the post, the eraseconfig command is not included
- so I extracted the rom.zip from RUU_Hero_HTC_WWE_1.76.405.1_R3_WWE_release_signed_NoDriver.exe
- tried to flash it, downgrade should be possible because of the goldcard
- but I now get the error "INFOchecking main version... FAILED (remote: 43 main version check fail)"
What can I do?
Could I extract the hboot from the 1.76.405.1_R3 and replace the one of 2.73.405.5 just to have the eraseconfig command?
Every kind of help is appreciated.
Thanks
André
Goldcards are handset specific as it has something to do with the serial number.
This MIGHT be the issue.
Really? On another post I read that they are specific to the sd-card, as one has to identify the unique id of the sd card and not of the handset.
Here's the link to the thread:
http://forum.xda-developers.com/showthread.php?t=648102
You sure?..... Ask your pal to do the "cat /sys/class/mmc_host/mmc1/mmc1:*/cid" bit using two different SD cards (yours and his own one) to see if the code is the same of or not.
..... or backup the goldcard your pal done you,... then make a new one yourself using whatever guide your using at the mo,... along with this one,..... http://thatsbadass.com/android/tag/cid/ ... <--that guide shows how to get your CID without plugging your phone in.
I tried it with another card and its another code. So I think it depends on the sd-card.
So, I think I tried flashing before I created the goldcard and that process stopped at the very beginning, saying something like cid check failed or so and not with that "main version check fail" message.
EDA-One said:
I tried it with another card and its another code. So I think it depends on the sd-card.
So, I think I tried flashing before I created the goldcard and that process stopped at the very beginning, saying something like cid check failed or so and not with that "main version check fail" message.
Click to expand...
Click to collapse
Aha,... OK,... You must be right,... apologies.
.... Have you tried using flashrec already?....
If I remember correctly, you cannot flash this version directly since it is actually a downgrade. I don't remember clearly how I managed to bring it up, either it was thanks to a Goldcard (I did experiment with that), or it was enough to patch the custom recovery image (see http://android.modaco.com/content/h...android-modaco-com-index-phpshowtopic-292396/).
Click to expand...
Click to collapse
not yet. but i will try now.
But I don't know, what should I try to flash with flashrec.
A new recovery rom? I think flashrec only allows *.img, or am I missing something?
...
...
...
OK,that worked.
Now I will try to flash the RUU_Hero_HTC_WWE_1.76.405.1_R3_WWE_release_signed.
updating or rather downgrading with the cyanogen recovery does not work. it says: Can't open /sdcard/HEROIMG_.......release_signed.zip(bad).
so i will try flashing via fastboot
Did you get this resolved?
No, it doesn't work.
Now I even got no wifi. Could not activate it.
Does there exist a custom rom, that I could flash and that contains a newer hboot, which contains the eraseconfig command?
Hi,
I had exactly the same problem and used that post from modaco to get out of it. As I understand it, you have reflashed the first RUU, so you have SD access but still no USB, right?
When I got to that stage, I didn't use the 2nd RUU at all, I just reflashed the new SPL (update-hero-hboot-1.76.2007-signed.zip) which opened up the fastboot oem eraseconfig option. I was on 1.76.0007 already (check the S-OFF is displayed on the fastboot screen, that means the goldcard is working AFAIK)
Flashing that SPL was enough, I think the oem commands are in there rather than the ROM itself (since in fastboot mode, the SPL is the only thing that is running).
Hope that helps.
Where can I get this one?
OK, found it and will try it.
OK, i could update the SPL.
But eraseconfig does not make any change.
Now that I got the engineering SPL, I hopefully find a solution.
I will dive deep inside the forum and try to find a way to get my USB up and running.
Many thanks till now.
I can't find a solution, usb and adb still do not work.
What I've done:
- Tried "fastboot oem eraseconfig" --> no change
- "fastboot oem readconfig" gives:
INFOindex:0x0, value:0x0
INFOindex:0x1, value:0x0
INFOindex:0x2, value:0x0
INFOindex:0x3, value:0x0
INFOindex:0x4, value:0x0
INFOindex:0x5, value:0x0
INFOindex:0x6, value:0x0
INFOindex:0x7, value:0x0
INFOindex:0x8, value:0x0
INFOindex:0x9, value:0x0
OKAY [ 0.023s]
finished. total time: 0.023s
-"fastboot oem boot" gives:
... INFOsetup_tag addr=0xA0000100 cmdline add=0x8F0841F0
INFOTAG:Ramdisk OK
INFOTAG:smi ok, size = 32
INFOTAG:hwid 0x1
INFOTAG:skuid 0x20800
INFOTAG:hero panel = 0x3
INFOTAG:engineerid = 0x3
INFODevice CID is not super CID
INFOCID is T-MOB101
INFOsetting.cid::T-MOB101
INFOserial number: HT97xxxxxxxx
INFOcommandline from head: no_console_suspend=1 console=null
INFOcommand line length =350
INFOactive commandline: board_hero.disable_uart3=0 board_hero.us
INFOb_h2w_sw=0 board_hero.disable_sdcard=0 smisize=32 androidbo
INFOot.baseband=6.35.06.18 androidboot.cid=T-MOB101 androidboot.
INFOcarrier=TMD androidboot.mid=HERO10000 androidboot.keycaps=qw
INFOertz androidboot.mode=normal androidboot.serialno=HT97xxxxxxxx
INFO71 androidboot.bootloader=1.76.2007 no_console_suspend=1 con
INFOsole=null
INFOaARM_Partion[0].name=misc
INFOaARM_Partion[1].name=recovery
INFOaARM_Partion[2].name=boot
INFOaARM_Partion[3].name=system
INFOaARM_Partion[4].name=cache
INFOaARM_Partion[5].name=userdata
INFOpartition number=6
INFOValid partition num=6
INFO0
INFO0
INFO69466957
INFO69784520
INFO69007473
INFO7473
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
FAILED (status read failed (Too many links))
finished. total time: 6.158s
Hmm, all the uart_disable and sdcard_disable are set to 0, so it looks like the eraseconfig has done its job (in that sense).
Just throwing a few ideas around here.
Do you have access to the SD card now and/or wi-fi now? I guess we really need a way to get access to the logs, but without USB you might need to use a file manager and try to find them... you want the equivalent of adb logcat basically...
when you plug-in a USB cable to the device, do any of the notifications come up on the hero and what does it say under the charging info, is it charging(AC) or charging(USB)?
Could just be the PC drivers if the device is detecting USB now?
Charging works in both cases (AC/USB).
Still got no USB-Connection, no connection notification is coming up on the device.
On the device I can access the sdcard.
WiFi is not working anymore.
Just flashed Modaco 3.2 and WiFi works again.
Now i have root access with a file explorer.
OK, I installed that aLogcat-App that saves the log to SD. I will try to create some logs, plugging in the usb cable.
So, heres the log. There's something strange going on, I think.
See my comments
I connected the USB-cable:
D/UsbConnectedReceiver( 248): ACTION_BATTERY_CHANGED
D/UsbConnectedReceiver( 248): unplugged = 1
//--> unplugged = 1 ?!?!
D/dalvikvm( 234): GC freed 2834 objects / 153480 bytes in 138ms
D/dalvikvm( 183): GC freed 315 objects / 14504 bytes in 91ms
D/dalvikvm( 143): GC freed 215 objects / 8544 bytes in 133ms
D/KeyguardUpdateMonitor( 95): receive ACTION_BATTERY_CHANGED
D/HtcLockScreen( 95): onRefreshBatteryInfo: 100
D/KeyguardViewMediator( 95): pokeWakelock(15000)
I/HtcLockScreen( 95): updateStatusViewByPriority
I disconnected the cable:
D/UsbConnectedReceiver( 248): ACTION_BATTERY_CHANGED
D/UsbConnectedReceiver( 248): unplugged = 0
//-> unplugged = 0 ?!?!
D/UsbConnectedReceiver( 248): USB Disconnected.
D/UsbConnectedReceiver( 248): Catch USB Disconnect Event, USB cable does really not exist.
D/UsbConnectedReceiver( 248): ADB Enable = true
// --> enable adb on disconnect ?
D/UsbConnectedReceiver( 248): ADB StartByMe = false
D/UsbConnectedReceiver( 248): Try to stop PSService.
Here is the log of a friend that has the hero too:
D/StatusBarPolicy( 136): cable plugged, mPluggedBatteryLevel=58
D/UsbConnectedReceiver( 300): ACTION_BATTERY_CHANGED
D/UsbConnectedReceiver( 300): unplugged = 1
D/KeyguardUpdateMonitor( 136): receive ACTION_BATTERY_CHANGED
D/UsbConnectedReceiver( 300): ACTION_BATTERY_CHANGED
D/UsbConnectedReceiver( 300): unplugged = 2
D/UsbConnectedReceiver( 300): USB Connected.
D/UsbConnectedReceiver( 300): mObexServerStarted=true
D/UsbConnectedReceiver( 300): mAtCommandServerStarted=false
D/UsbConnectedReceiver( 300): Try to start ATCommandService.
D/PSService( 300): onStart()
D/UsbConnectedReceiver( 300): Show Notification...
D/UsbConnectedReceiver( 300): Server Start Up. ServerType=1 ServerStatus=1
D/UsbConnectedReceiver( 300): mObexServerStarted=true mAtCommandServerStarted=true
D/UsbConnectedReceiver( 300): Show Notification...
D/MountListener( 136): handleEvent ums_connected
D/dalvikvm( 2363): GC freed 1621 objects / 82560 bytes in 129ms
D/dalvikvm( 300): GC freed 3754 objects / 615400 bytes in 106ms
D/dalvikvm( 300): GC freed 4448 objects / 776848 bytes in 101ms
D/MountListener( 136): handleEvent ums_disabled
D/MountListener( 136): handleEvent ums_disconnected
D/KeyguardUpdateMonitor( 136): receive ACTION_BATTERY_CHANGED
D/HtcLockScreen( 136): onRefreshBatteryInfo: 33
D/KeyguardViewMediator( 136): pokeWakelock(15000)
I/HtcLockScreen( 136): updateStatusViewByPriority
D/UsbConnectedReceiver( 300): ACTION_BATTERY_CHANGED
D/UsbConnectedReceiver( 300): unplugged = 0
D/UsbConnectedReceiver( 300): USB Disconnected.
D/UsbConnectedReceiver( 300): Catch USB Disconnect Event, USB cable does really not exist.
D/UsbConnectedReceiver( 300): ADB Enable = true
D/UsbConnectedReceiver( 300): ADB StartByMe = false
D/UsbConnectedReceiver( 300): Try to stop PSService.
I/ActivityManager( 136): Stopping service: com.htc.android.psclient/.PSService
D/UsbConnectedReceiver( 300): Server Start Up. ServerType=1 ServerStatus=0
D/dalvikvm( 2318): GC freed 8615 objects / 518960 bytes in 121ms
D/dalvikvm( 383): GC freed 3095 objects / 170360 bytes in 112ms
D/dalvikvm( 206): GC freed 2271 objects / 398152 bytes in 140ms

[Q] wifi doesn't work at any of android builds

Hi all,
I have a t-mobile phone and tried to install android 2.2. there. I used mdeejay's and darkStone's builds, but wifi didn't work at any of them. I've found a person who uses T-mobile hd2 too and installed the same versions of rom and radio. It didn't helped. In windows mobile wifi works well.
Could you please advice how to hande it? Did anyone face the same problem?
Thank you in advance.
#did some debug via adb:
I suppose that the red line below tells about reason.. But I haven't dealt with WPA on android before.. Any help is appreciated.
D/WifiService( 1916): setWifiEnabled( mAirplaneModeOverwridden=)false
I/WifiHW ( 1916): wifi_load_driver enter
D/NetSharing_NSReceiver( 2298): onReceive : android.net.wifi.WIFI_STATE_CHANGED
D/NetSharing( 2298): wifi enabled change, state = false
I/WifiHW ( 1916): wifi_load_driver end right 3
I/WifiHW ( 1916): wifi_start_supplicant enter
I/WifiHW ( 1916): wifi_start_supplicant end right 2
D/WifiService( 1916): ACTION_BATTERY_CHANGED pluggedType: 2
I/wpa_supplicant( 2771): CTRL-EVENT-STATE-CHANGE id=-1 state=0 BSSID=00:00:00:00
:00:00
E/wpa_supplicant( 2771): Failed to disable WPA in the driver.
D/NetSharing_NSReceiver( 2298): onReceive : android.net.wifi.WIFI_STATE_CHANGED
D/NetSharing( 2298): wifi enabled change, state = true
D/PowerManagerService( 1916): New lightsensor value:40, lcdValue:90
D/lights ( 1916): set_light_buttons
D/lights ( 1916): set_light_keyboard
E/SettingsWifiLayer( 2298): Unable to scan for networks
D/SurfaceFlinger( 1916): Layer::setBuffers(this=0x6257a8), pid=2298, w=1, h=1
D/SurfaceFlinger( 1916): Layer::setBuffers(this=0x6257a8), pid=2298, w=1, h=1
D/SurfaceFlinger( 1916): Layer::requestBuffer(this=0x6257a8), index=0, pid=2298,
w=350, h=85 success
E/WifiHW ( 1916): Supplicant not running, cannot connect
E/SettingsWifiLayer( 2298): Unable to scan for networks
D/SurfaceFlinger( 1916): Layer::setBuffers(this=0x4ca268), pid=2298, w=1, h=1
D/SurfaceFlinger( 1916): Layer::setBuffers(this=0x4ca268), pid=2298, w=1, h=1
D/SurfaceFlinger( 1916): Layer::requestBuffer(this=0x4ca268), index=0, pid=2298
w=350, h=85 success
E/WifiHW ( 1916): Supplicant not running, cannot connect
V/WifiStateTracker( 1916): Supplicant died unexpectedly
D/WifiStateTracker( 1916): Reset connections and stopping DHCP
D/NetUtils( 1916): ifc_get_info addr=0 !
D/WifiStateTracker( 1916): Disabling interface
D/WifiService( 1916): setWifiEnabled( mAirplaneModeOverwridden=)false
D/WifiStateTracker( 1916): Reset connections and stopping DHCP
D/NetUtils( 1916): ifc_get_info addr=0 !
D/NetSharing_NSReceiver( 2298): onReceive : android.net.wifi.WIFI_STATE_CHANGED
D/NetSharing( 2298): wifi enabled change, state = true
D/WifiStateTracker( 1916): Disabling interface
I/WifiHW ( 1916): wifi_stop_supplicant enter
I/WifiHW ( 1916): wifi_stop_supplicant end right 1
I/WifiHW ( 1916): wifi_unload_driver enter
I/WifiHW ( 1916): wifi_unload_driver end right 2
D/NetSharing_NSReceiver( 2298): onReceive : android.net.wifi.WIFI_STATE_CHANGED
D/NetSharing( 2298): wifi enabled change, state = false
how to set up MAC address for android builds (except startup.txt)?
Hi again,
I did some search and found that the core of the problem is in getting MAC address for wifi. (as dmsg says). Exactly the same problem was for Touch2, Tilt and other devices (http://forum.xda-developers.com/showthread.php?p=9211659) and it was resolved after they corrected wifi-nvram.txt. This file is responsible for setting up MAC address there, but I couldn't find it at builds for hd2.
if anybody knows what file is used to set up MAC address for wifi, I would be very appreciated.
Thanks!
I believe they just checked for their WiFi mac address from one of the following locations:
Settings->About phone->Status
Wireless & Networks -> WiFi Settings -> Menu Button -> Advanced
Then they edited the nvram.txt file @ /system/lib/hw/wifi/nvram.txt to include the proper MAC address.
Thanks for the answer!
Unfortunatelly wireless settings are not available until wifi is turned on.
I investigated the problem deeper and found that the reason could be in wifi hardware initialization. I did dmesg and saw the following:
wlan: wifi_set_power = 1
htcleo_wifi_power: 1
wlan: wifi_set_carddetect = 1
htcleo_wifi_set_carddetect: 1
mmc0: card_present 1
mmc0: Slot status change detected (0 -> 1)
wlan: Dongle Host Driver, version 4.218.204.2
mmc0: queuing CIS tuple 0x91 length 3
mmc0: new high speed SDIO card at address 0001
wlan: DHD: dongle ram size is set to 294912(orig 294912)
wlan: dhd_bus_rxctl: resumed on timeout
wlan: firmware version: ver
wlan: Return_dpc value is : 0
wlan: stop poll
wlan: dhd_bus_rxctl: resumed on timeout
wlan: dhd_preinit_ioctls: can't get MAC address , error=-110
wlan: dhdsdio_probe: failed
Since in windows mobile wifi does work I used the firmware files from WM: nvram.txt and rtecdc1.bin. As it turned out nvram in android is located in /proc/calibraion. But unfortunatelly it didn't help. So, I think that the problem is in bcm4329.ko driver. I'm not sure why other people with the same hd2 (t-mobile US) and the same ROM/RADIO/Android have no such issue. Perhaps my broadcomm hardware has a problem which is bypassed in windows, but not in Android.
I wonder if there is a way to get more detailed info than dmesg and logcat give (except building andoid sources of course ).
I don't know if it can help, but still, I'll say it anyway.
I think i had the same problem some times ago.
Wifi in android wouln't work, but was perfectly working in winmo.
it seems that if wifi is on in winmo when you boot on android, the wifi device seems to be blocked in some way.
Do you have wifi enabled in winmo? if yes, try to disable it, and boot on android to see if it works.
Hi kushulain,
Thanks for the advice! (I've almost started to build andriod by myself to find out the reason..) Unfortunatelly wifi was turned off when android was booting.
But this is another point to play around. I haven't tried to boot andriod with wifi turned on.
Thanks!
Just tried to boot andriod with wifi turned on. The device hangs at the beginning of the booting (even before screen with 'htc' appears). I think it is connected to my problem.
Did someone have similar problems?
Hey, I have the same problem, did you find any solution ?
Guys have you tried to change the radio part of the phone with a suitable one?
canavaro said:
Hey, I have the same problem, did you find any solution ?
Click to expand...
Click to collapse
hi, I didn't fix it actually due to lack of time. I tried to use wm hw init files in Android, but it didn't help. There is a score of my posts on this forum regarding this topic so you can find exactly what I tried. The funny thing is that WiFi works in wp7.
To stealth21
yes, that was the first thing I tried.

[Q] ICS OTG ZTE MF820 LTE dongle

when I use OTG cable plug the ZTE MF820 LTE Dongle, android can detect its model but the 3g/4g not work .
I checked there is a file
/etc/usb_modeswitch.d/19d2_0166
###########################
ZTE MF820 4G LTE
DefaultVendor= 0x19d2
DefaultProduct=0x0166
TargetVendor= 0x19d2
TargetProduct=0x0167
MessageEndpoint=0x01
MessageContent=55534243123456782400000080000685000000240000000000000000000000
CheckSuccess=20
here is a part of the message from the logcat:
D/MountService( 146): sendStorageIntent Intent { act=unmounted dat=file:///mnt/usbhost1 (has extras) }
D/MountService( 146): volume state changed for /mnt/usbhost1 (unmounted -> removed)
D/MountService( 146): sendStorageIntent Intent { act=android.intent.action.MEDIA_REMOVED dat=file:///mnt/usbhost1 (has extras) }
D/[CORE_SERVICE]( 2057): Receive media broadcast
D/[NOTIFICATION]( 2057): ignore a notification because of not accepted
I/StorageNotification( 213): Media {/mnt/usbhost1} state changed from {unmountable} -> {unmounted}
D/VoldCmdListener( 82): volume shared /mnt/sdcard ums
I/StorageNotification( 213): Media {/mnt/usbhost1} state changed from {unmounted} -> {removed}
.
.
.
D/APPTrafficLogic( 1867): 10053--android.process.acore--0--0--
I/USB3G ( 92): event { 'add', '/devices/platform/sw_hcd_host0/usb1/1-1', 'usb', '', 189, 9 }
I/USB3G ( 92): path : '/sys/devices/platform/sw_hcd_host0/usb1/1-1'
I/USB3G ( 92): VID :size 5,vid_path '/sys/devices/platform/sw_hcd_host0/usb1/1-1/idVendor',VID '19d2
I/USB3G ( 92): '.
I/USB3G ( 92): PID :size 5,Pid_path '/sys/devices/platform/sw_hcd_host0/usb1/1-1/idProduct',PID '0167
I/USB3G ( 92): '.
I/USB3G ( 92): cmd=/system/etc/usb_modeswitch.sh /system/etc/usb_modeswitch.d/19d2_0167 &,
I/USB3G ( 92): excute ret : 0,err:No such file or directory
what is the problem? thank you for any advice.
I rename the 19d2_0166 to 19d2_0167
and run
/# system//etc/usb_modeswitch.sh system/etc/usb_modeswitch.d/19d2_0167
Reading config file: /etc/usb_modeswitch.d/19d2_0167
* usb_modeswitch: handle USB devices with multiple modes
* Version 1.2.0 (C) Josua Dietze 2011
* Based on libusb0 (0.1.12 and above)
! PLEASE REPORT NEW CONFIGURATIONS !
DefaultVendor= 0x19d2
DefaultProduct= 0x0166
TargetVendor= 0x19d2
TargetProduct= 0x0167
TargetClass= not set
TargetProductList=""
DetachStorageOnly=0
HuaweiMode=0
SierraMode=0
SonyMode=0
QisdaMode=0
GCTMode=0
KobilMode=0
SequansMode=0
MobileActionMode=0
CiscoMode=0
MessageEndpoint= not set
MessageContent="55534243123456782400000080000685000000240000000000000000000000"
NeedResponse=0
ResponseEndpoint= not set
InquireDevice disabled
Success check enabled, max. wait time 20 seconds
System integration mode disabled
usb_set_debug: Setting debugging level to 15 (on)
usb_os_find_busses: Found 003
usb_os_find_busses: Found 002
usb_os_find_busses: Found 001
usb_os_find_devices: Found 001 on 003
usb_os_find_devices: Found 002 on 002
usb_os_find_devices: Found 001 on 002
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 019 on 001
usb_os_find_devices: Found 001 on 001
error obtaining child information: Inappropriate ioctl for device
Looking for target devices ...
searching devices, found USB ID 1d6b:0001
searching devices, found USB ID 0bda:8176
searching devices, found USB ID 1d6b:0002
searching devices, found USB ID 19d2:0167
found matching vendor ID
found matching product ID
adding device
searching devices, found USB ID 1d6b:0001
Found devices in target mode or class (1)
Looking for default devices ...
searching devices, found USB ID 1d6b:0001
searching devices, found USB ID 0bda:8176
searching devices, found USB ID 1d6b:0002
searching devices, found USB ID 19d2:0167
found matching vendor ID
searching devices, found USB ID 1d6b:0001
No devices in default mode found. Nothing to do. Bye.
is that miss something ?

[DEV- MOD] [Under Development] Multiple USB drives MTCB Units

Hey guys,
Currently i`m digging into this matter. So here's the concept:
[HU] - one of the back USB's
|
[USB Hub] - powered form an external power supply (external 5V)
| |
U1 U2 - (32GB USB Drives)
A.) Current behaviour
- only the first inserted USB drive get's mounted under /mnt/usb_storage2
- the second usb drive is recognised by the kernel and does not get mounted by the system (not assigned to any "drive letter" so to speak(i think)).
B.) Current investigations:
B.1 ) by unpacking the boot.img - fstab.rk30board.bootmode.*
Code:
/devices/platform/usb20_otg/usb /mnt/usb_storage vfat defaults voldmanaged=usb_storage:auto
/devices/platform/usb20_host/usb /mnt/usb_storage2 vfat defaults voldmanaged=usb_storage2:auto
B.2) by unpacking the boot.img - init.rk30board.rc
Code:
[13] export THIRD_VOLUME_STORAGE /mnt/usb_storage
[14] mkdir /mnt/usb_storage 0000 system system
[15] export THIRD_VOLUME_STORAGE2 /mnt/usb_storage2
[16] mkdir /mnt/usb_storage2 0000 system system
On the Application Side, for example MTCAPKInstall_source/com/hct/apkinstall/DevListAdapter.java
Code:
} else if (path.equals("/mnt/usb_storage")) {
holder.Image.setImageResource(R.drawable.usbhost);
holder.ImageName.setText(this.mContext.getString(R.string.usb1));
} else if (path.equals("/mnt/usb_storage2")) {
holder.Image.setImageResource(R.drawable.usbhost);
holder.ImageName.setText(this.mContext.getString(R.string.usb2));
This can be solved easily by creating a for, or by duplication each else if (the copy/paste way )
I need to do some more tests... i`m also interested for your opinions/experience with this (What have you tested, What worked, What did not work, Why is not working, etc..)
So cheers to everyone and keep you posted
So far i rulled out the usb driver, internal hub.. It has something to do with the block creation and vold...
Will dig more tomorrow(i hope)
okey, so baseline the issue is related to VOLD
VOLD does not generate the block device for the new devices... i`m not 100% sure that VOLD handles the block device generation
for the time being i managed to mount 3 separate partitions from the same USB storage -> by doing this i ruled out the kernel itself, the irq assignment, etc..
I need to dig deeper into VOLD and to see exactly what is the process for generating the block device eg (/dev/block/vold/8:X)
from this point it would be nice to exchange some experience with someone that really know how things work on Android, i`m an iOS user, and the HU is my first Android System
I can't help as haven't gone down the road of digging to deep into kernels and Roms due to other commitments..
But just want to offer words of encouragement as you are working towards a good course..
I don't use a mobile modem and so at the moment that spare usbport is doing nothing. Would be nice to load it up with a spare USB drive I have around here .
That then brings up the powering up thread which the boys have already sorted..
So once you crack this and get a kernel mode going we are good to go..
Sent from my SM-G900I using Tapatalk
I tried to have a look in the binary code of vold shipped with the firmware, but friday was short... I'll continue my work next week
Keep you guys posted
In the past i did some test with a 4 Port USB hub. I connected several USB sticks and a 350 gb harddisk. They were not recognised by rootexplorer or android itself, but ESF file Explorer did recognised all of the devices.
Another strange thing is that when i connect a USB RTL dab+ dongle on the First USB Port on my hui and the harddisk on the other usb port my GPS is not working propperly.
well i`m 100% sure that the hub is not the issue, because:
<<1'st usb drive>>
<6>[ 1757.992589] usb 2-1.3: new high speed USB device number 30 using usb20_host
<6>[ 1758.093203] usb 2-1.3: New USB device found, idVendor=0781, idProduct=5204
<6>[ 1758.093230] usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
<6>[ 1758.093282] usb 2-1.3: Product: Cruzer Crossfire
<6>[ 1758.093303] usb 2-1.3: Manufacturer: SanDisk Corporation
<6>[ 1758.093322] usb 2-1.3: SerialNumber: 000016A29874531B
<4>[ 1758.094142] --mtc usb storage 2-1.3 0781 5204
<6>[ 1758.094989] scsi11 : usb-storage 2-1.3:1.0
<5>[ 1759.092957] scsi 11:0:0:0: Direct-Access SanDisk Cruzer 4.05 PQ: 0 ANSI: 2
<5>[ 1759.094087] sd 11:0:0:0: [sda] 16055949 512-byte logical blocks: (8.22 GB/7.65 GiB)
<5>[ 1759.094577] sd 11:0:0:0: [sda] Write Protect is off
<7>[ 1759.094601] sd 11:0:0:0: [sda] Mode Sense: 03 00 00 00
<3>[ 1759.095072] sd 11:0:0:0: [sda] No Caching mode page present
<3>[ 1759.095095] sd 11:0:0:0: [sda] Assuming drive cache: write through
<3>[ 1759.098162] sd 11:0:0:0: [sda] No Caching mode page present
<3>[ 1759.098183] sd 11:0:0:0: [sda] Assuming drive cache: write through
<6>[ 1759.100316] sda: sda1
<3>[ 1759.104583] sd 11:0:0:0: [sda] No Caching mode page present
<3>[ 1759.104621] sd 11:0:0:0: [sda] Assuming drive cache: write through
<5>[ 1759.104663] sd 11:0:0:0: [sda] Attached SCSI removable disk
<7>[ 1759.846560] SELinux: initialized (dev sda1, type vfat), uses genfs_contexts
<<2'nd usb drive>>
<6>[ 1956.392593] usb 2-1.2: new high speed USB device number 31 using usb20_host
<6>[ 1956.493577] usb 2-1.2: New USB device found, idVendor=0951, idProduct=1666
<6>[ 1956.493616] usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
<6>[ 1956.493647] usb 2-1.2: Product: DataTraveler 3.0
<6>[ 1956.493666] usb 2-1.2: Manufacturer: Kingston
<6>[ 1956.493683] usb 2-1.2: SerialNumber: 60A44C425294BE10A9820D20
<4>[ 1956.494632] --mtc usb storage 2-1.2 0951 1666
<4>[ 1960.190620] ~ arm_rev_16bits err0 0
the GUI applications are dependent of Device Block Assignment, as you can clearly see, kernel recognises both USB Storage devices, but only the first is assigned with a block device.
okey, so i had a chance to check with IDA the vold binary from our units... seems that vold binary is custom than from other rom's
i will do some tests on the unit itself with a modified version of vold to see what happens
Later Edit,
vold has nothing to do with the block assignment ... on the front USB port also known by the unit : usb20_otg works like a charm... i added 4 USB Drivers each one named accordingly -> sda, sdb, etc.. i managed to mount them manually -> success
On the rear USB also known by the unit usb20_hub it still does not work, VOLD was stopped and removed during tests
clearly things do not add up.. and VOLD so far seems to be ok..
i ran out of ideas
i'm not a developer, but if you find a solution for that problem, you'll be a hero. hope you have finally the idea that will be the right one

Categories

Resources