Closed GoogleCodeExporter closed 8 years ago
On what kind of filesystem you made tests? Could you show part of shell screen
with unproper results?
Original comment by adrian.s...@gmail.com
on 14 Aug 2011 at 9:07
I used adb shell to check on the filenames. This problem showed up on my archos
7it with Urukdroid running. I checked with my other dev devices archos 7HTv2,
arnova 7 and archos 10it, with either original or custom firmware (no uruk)
installed. No problem there. In fact, the issue popped up when I tried my
commercial app on urukdroid for the first time. I have to admit hat i didn't
crosscheck using the original archos firmware on the 7it, but with all my other
archos non-uruk devices. So this problem is either inherted from archos 7it
firmware or its uruk specific.
I use update files in my app which happen to have names in upper-case only.
When looking for the files in my java app, I use the upper-case name taken from
final static strings for comparison. On the 7it uruk, the files could not be
found because of case-sensitivity.
Please note that my app programmatically copies the files to the device from
external sd-card to internal memory. The same app, using the same sd-card on
any other android device i could get hold of worked just fine. I will provide
screenshot of my adb session on Tuesday
Original comment by quizdr...@gmail.com
on 15 Aug 2011 at 3:24
You can copy/paste from adb - it does not have to be screenshot.
Anyway - I can't reproduce any of this issues. That's why I've asked on what
filesystem did you check this behaviour. FAT is case insensitive, EXT4 (that is
rootfs and datafs) are case sensitive. I'm kind of sceptic on what you are
saying since you mentioned that "ls" and "ls -l" give different results - this
is quite impossible.
Original comment by adrian.s...@gmail.com
on 15 Aug 2011 at 7:11
See my adb shell session screenshot attached. It also includes results of the
mount command.
Original comment by quizdr...@gmail.com
on 17 Aug 2011 at 7:38
Attachments:
To be honest - it's quite normal for me. This is FAT partition. There are some
translation made so case insensitive filesystems (like fat) will work on Unix
way, where everything is case sensitive. That's why there are such a strange
"things" going on. But I expect the same happens on stock FW. You could
probably change some mount parameters (to change a bit this behaviour), like
"check", "conv" options, but I think it's normal :).
I close "the bug" - but if you still think there is something wrong, fell free
to reopen it.
Original comment by adrian.s...@gmail.com
on 22 Aug 2011 at 3:54
Original issue reported on code.google.com by
quizdr...@gmail.com
on 1 Aug 2011 at 3:12