Forums | developer.brewmp.com Forums | developer.brewmp.com

Developer

Forums

Forums:

On the moto T720 I had no problem deleting/opening in the app directory a file named "appname.properties". When I tried to delete/open the same name in the shared directory, the phone crashed every time. The crash went away when I changed the name to "appname.dat". Has anyone else seen similar file naming limitations on this or other phones?

brew phones usually do not allow full path to exceed 32 chars. but t720's error tolerance is not that good.
i once tried to create a deep directory like this:
/myapp0000/aaaaaaaa/aaaaaaaa/
then tried to store a file like "abcdefghijkl.abc" into it. the file saving failed because the whole thing exceeds 32. but from then on the phone could no longer create or delete directories, no matter i tried to create/delete from apploader or brew app. the phone crashed on such requests.
they all say file system is corrupted, but t720 cannot do reformatting. i even tried to send the phone to qualcomm but they failed to fix this. a brew support told me t720 has defects on file system.

brew phones usually do not allow full path to exceed 32 chars. but t720's error tolerance is not that good.
i once tried to create a deep directory like this:
/myapp0000/aaaaaaaa/aaaaaaaa/
then tried to store a file like "abcdefghijkl.abc" into it. the file saving failed because the whole thing exceeds 32. but from then on the phone could no longer create or delete directories, no matter i tried to create/delete from apploader or brew app. the phone crashed on such requests.
they all say file system is corrupted, but t720 cannot do reformatting. i even tried to send the phone to qualcomm but they failed to fix this. a brew support told me t720 has defects on file system.

Interesting info, thanks. The T720 file system is fragile, that's for sure. The path to the file I was attempting to delete was only 26 chars though, so I think it was the length of the extension that caused the problem, and only in the shared directory.

Interesting info, thanks. The T720 file system is fragile, that's for sure. The path to the file I was attempting to delete was only 26 chars though, so I think it was the length of the extension that caused the problem, and only in the shared directory.

I think there´s a limitation on the file name too, I once tried to copy a file and it wouldn´t copy, only when I changed the file name to something smaller it worked..

I think there´s a limitation on the file name too, I once tried to copy a file and it wouldn´t copy, only when I changed the file name to something smaller it worked..

yes, i did this too.
i think it is limited by the full path, that is, full directory from "/" until the end of file name.
Quote:Originally posted by Marcel
I think there´s a limitantion on the file name too, I once tried to copy a file and it wouldn´t copy, only when I changed the file name to something smaller it worked..

yes, i did this too.
i think it is limited by the full path, that is, full directory from "/" until the end of file name.
Quote:Originally posted by Marcel
I think there´s a limitantion on the file name too, I once tried to copy a file and it wouldn´t copy, only when I changed the file name to something smaller it worked..

I think its probably best to use 8.3 filenames everywhere, give everything 3 letter extensions, and not get too cute with sub directories. You never know what kind of weirdness might be uncovered in a particular device, but you can be sure they've tested the basics.

I think its probably best to use 8.3 filenames everywhere, give everything 3 letter extensions, and not get too cute with sub directories. You never know what kind of weirdness might be uncovered in a particular device, but you can be sure they've tested the basics.

Hi folks,
we are in the same situation... we have already got two directories "stuck" on different devices (T720 and CDM9500), and we just don't seem to be able to get rid of them or even access them. The weirdest thing is that the dirs are only 14-chars wide (including the starting '/'); 13-chars pathnames work just fine.
Anyone already succeeded on working around this kind of problem?
TIA
Andre

Hi folks,
we are in the same situation... we have already got two directories "stuck" on different devices (T720 and CDM9500), and we just don't seem to be able to get rid of them or even access them. The weirdest thing is that the dirs are only 14-chars wide (including the starting '/'); 13-chars pathnames work just fine.
Anyone already succeeded on working around this kind of problem?
TIA
Andre

so far no solution yet.
i still have that long dir in my t720, never got rid of it. neither could i create new dir. but other than dir problems, everything works well.
this t720 is becoming even more funny recently. i tried a master reset to see if it helps. but after master reset, the long dir is till there, just all files are gone. the surprising thing is, this master reset didn't clear the test-bit. i can still load apps to it and test... it seems the phone gets stuck with current status, no way to get better, no way to get worse.

so far no solution yet.
i still have that long dir in my t720, never got rid of it. neither could i create new dir. but other than dir problems, everything works well.
this t720 is becoming even more funny recently. i tried a master reset to see if it helps. but after master reset, the long dir is till there, just all files are gone. the surprising thing is, this master reset didn't clear the test-bit. i can still load apps to it and test... it seems the phone gets stuck with current status, no way to get better, no way to get worse.

Hi samsonsu, thks for sharing your experience.
"... neither could i create new dir." Do you mean you are not able to upload any other app ever since this problem happened??
The T720 is proving to be a real PITA -- porting apps to it has not been an easy task :mad:
Anyone tried Motorola support?

Hi samsonsu, thks for sharing your experience.
"... neither could i create new dir." Do you mean you are not able to upload any other app ever since this problem happened??
The T720 is proving to be a real PITA -- porting apps to it has not been an easy task :mad:
Anyone tried Motorola support?

right. when i tried to create new dir (either from apploader or from IFILEMGR), the phone crashed. (same when i tried to delete any dir).
since each app needs its own directory, i'm not able to upload any new app to this phone. what i can do is to use existing apps only, because their dirs are already there.
Quote:Originally posted by blueser
"... neither could i create new dir." Do you mean you are not able to upload [b]any other app ever since this problem happened??
[/B]

right. when i tried to create new dir (either from apploader or from IFILEMGR), the phone crashed. (same when i tried to delete any dir).
since each app needs its own directory, i'm not able to upload any new app to this phone. what i can do is to use existing apps only, because their dirs are already there.
Quote:Originally posted by blueser
"... neither could i create new dir." Do you mean you are not able to upload [b]any other app ever since this problem happened??
[/B]

...!!! Man, this is really ugly. I am starting to really dislike this device... Have you tried to contact Motorola about this?

...!!! Man, this is really ugly. I am starting to really dislike this device... Have you tried to contact Motorola about this?

Have you tried marking all the files in the stuck directories as "unrestricted" via the Perl interface to the AppLoader? I don't think that these flags are exposed by the AppLoader GUI.
I was experimenting with the "permanent" and "readonly" attributes, and the presence of a permanent file will block the whole folder from deleting. Fortunately, you can remark it "unrestricted" and it'll delete just fine.
This was on a T720. Hope it helps.
-Jesse

Have you tried marking all the files in the stuck directories as "unrestricted" via the Perl interface to the AppLoader? I don't think that these flags are exposed by the AppLoader GUI.
I was experimenting with the "permanent" and "readonly" attributes, and the presence of a permanent file will block the whole folder from deleting. Fortunately, you can remark it "unrestricted" and it'll delete just fine.
This was on a T720. Hope it helps.
-Jesse

Thks Jesse, this looks promising :) I will test it ASAP, and will post back my results here. samsonsu: please post back here any results you might have as well, ok?

Thks Jesse, this looks promising :) I will test it ASAP, and will post back my results here. samsonsu: please post back here any results you might have as well, ok?

i just tried. here is my perl code
use lib "${ENV{BREWTOOLSDIR}}\\BREW Perl Interface";
use BREWPerlIF;
my $dll_name = "$ENV{BREWTOOLSDIR}\\OEMLayer\\QCOMOEM.dll";
my $port = $ARGV[0];
if(! $port || $port !~ /^com\d$/i) {
print "please specify com port in command line. i.e., COM6\n";
exit 1;

print "connecting to $port: " ;
BREWPerlIF::ConnecttoDevice($port, $dll_name ) || die "ERROR: failed to connect $port\n";
print "successful\n";
print "setting unrestricted attr: ";
BREWPerlIF::SetDeviceFileAttribute("/the/looooong/dir", 0x00ff) || die "ERROR: failed to set attr\n";
print "successful\n";
print "deleting dir: ";
BREWPerlIF::DeleteDeviceDir("/the/looooong/dir") || die "ERROR: failed to delete dir\n";
print "successful\n";
printf "disconnecting from device: " ;
BREWPerlIF::ReleaseDevice() || die "ERROR: failed to disconnect from $port\n";
print "successful\n";
execute it, and i got output:
connecting to COM4: successful
setting unrestricted attr:
Error: could not read from the device EFS
ERROR: failed to set attr

i just tried. here is my perl code
use lib "${ENV{BREWTOOLSDIR}}\\BREW Perl Interface";
use BREWPerlIF;
my $dll_name = "$ENV{BREWTOOLSDIR}\\OEMLayer\\QCOMOEM.dll";
my $port = $ARGV[0];
if(! $port || $port !~ /^com\d$/i) {
print "please specify com port in command line. i.e., COM6\n";
exit 1;

print "connecting to $port: " ;
BREWPerlIF::ConnecttoDevice($port, $dll_name ) || die "ERROR: failed to connect $port\n";
print "successful\n";
print "setting unrestricted attr: ";
BREWPerlIF::SetDeviceFileAttribute("/the/looooong/dir", 0x00ff) || die "ERROR: failed to set attr\n";
print "successful\n";
print "deleting dir: ";
BREWPerlIF::DeleteDeviceDir("/the/looooong/dir") || die "ERROR: failed to delete dir\n";
print "successful\n";
printf "disconnecting from device: " ;
BREWPerlIF::ReleaseDevice() || die "ERROR: failed to disconnect from $port\n";
print "successful\n";
execute it, and i got output:
connecting to COM4: successful
setting unrestricted attr:
Error: could not read from the device EFS
ERROR: failed to set attr

Did you try something like:
BREWPerlIF::SetDeviceFileAttribute("/the/looooong/dir/fileA", 0x00ff) || die "ERROR: failed to set attr\n";
BREWPerlIF::SetDeviceFileAttribute("/the/looooong/dir/fileB", 0x00ff) || die "ERROR: failed to set attr\n";
BREWPerlIF::SetDeviceFileAttribute("/the/looooong/dir/fileC", 0x00ff) || die "ERROR: failed to set attr\n";
I my case, the permanent attribute was on one of the files, but that blocked the entire directory tree from being deleted.
If that doesn't work, well, I'm out of ideas.

Did you try something like:
BREWPerlIF::SetDeviceFileAttribute("/the/looooong/dir/fileA", 0x00ff) || die "ERROR: failed to set attr\n";
BREWPerlIF::SetDeviceFileAttribute("/the/looooong/dir/fileB", 0x00ff) || die "ERROR: failed to set attr\n";
BREWPerlIF::SetDeviceFileAttribute("/the/looooong/dir/fileC", 0x00ff) || die "ERROR: failed to set attr\n";
I my case, the permanent attribute was on one of the files, but that blocked the entire directory tree from being deleted.
If that doesn't work, well, I'm out of ideas.

no. that dir is already empty. (master reset erased all files in it, but kept the dir structure)
Quote:Originally posted by jhw
Did you try something like:
BREWPerlIF::SetDeviceFileAttribute("/the/looooong/dir/fileA", 0x00ff) || die "ERROR: failed to set attr\n";
BREWPerlIF::SetDeviceFileAttribute("/the/looooong/dir/fileB", 0x00ff) || die "ERROR: failed to set attr\n";
BREWPerlIF::SetDeviceFileAttribute("/the/looooong/dir/fileC", 0x00ff) || die "ERROR: failed to set attr\n";
I my case, the permanent attribute was on one of the files, but that blocked the entire directory tree from being deleted.
If that doesn't work, well, I'm out of ideas.

no. that dir is already empty. (master reset erased all files in it, but kept the dir structure)
Quote:Originally posted by jhw
Did you try something like:
BREWPerlIF::SetDeviceFileAttribute("/the/looooong/dir/fileA", 0x00ff) || die "ERROR: failed to set attr\n";
BREWPerlIF::SetDeviceFileAttribute("/the/looooong/dir/fileB", 0x00ff) || die "ERROR: failed to set attr\n";
BREWPerlIF::SetDeviceFileAttribute("/the/looooong/dir/fileC", 0x00ff) || die "ERROR: failed to set attr\n";
I my case, the permanent attribute was on one of the files, but that blocked the entire directory tree from being deleted.
If that doesn't work, well, I'm out of ideas.