Toolbox df crops decimal places, usb-detect is delayed
Got it by myself.
df command crops the numerals behind the decimal point in the routine printsize (https://github.com/android/platform_...r/toolbox/df.c) busybox df shows the complete value. So this is just optically and I can use the whole capacity of the filesystem on that memstick.
It takes this time for the kernel to detect a new usb-device, when I pull out an other usb-device before. That has nothing to do with the model or the manufactorer of that device.
sorry to bother.
DSC is supporting USB-OTG with memory-sticks, mouse and even my old keyboard works on the streak over a powered usb-hub. Thank you for that.
I put in different usb-memory sticks with very different results:
* a 4 GB generic mem stick 3538:0054 took very long until vold mounted it. It showed 4.04 GB/3.76 GiB in dmesg but df showed only 3 GB under /mnt/usbdisk
* a 2 GB cnmemory mem stick 090c:1000 was mounted very fast and showed 2.07 GB / 1.93 GiB in dmesg but df showed only 1 GB under /mnt/usbdisk
* a 8 GB spaceloop mem stick 090c:1000 was mounted very fast and showed 7.98 GB/7.42 GiB in dmesg but df showed only 7 GB under /mnt/usbdisk
I had never problems with these sticks on my laptop, only android shows their space rounded down this extreme. Can someone confirm this? Is this just optically or will I get into trouble when I use the stick to full capacity?
Why do some sticks took > 30 secs until vold mounts them and others are mounted instantly?
Got the same effect with a generic usb-otg-cable on the mini-usb-port of the av-media-dock and a custom PDMI/usb-otg-cable I soldered myself.
Cloud storage services like Dropbox or Google Drive have grown in popularity dramatically … more
XDA Developers was founded by developers, for developers. It is now a valuable resource for people who want to make the most of their mobile devices, from customizing the look and feel to adding new functionality. Are you a developer?