Using Jobb Tool In Android
Solution 1:
You can also get following error with the jobb-Tool (at least in windows with the jobb.bat), if you have many many files.
de.waldheinz.fs.fat.Directory Full Exception: directory is full
This is, because the obb file format is saved in FAT16, whitch only allows 512 entries/files in the root directory
On Windows: if you have a folder "data" whith lost of pictures, and copied to the android sdk-tools directory
- data/1.jpg
- data/2.jpg
- data/3.jpg
- data/...
- data/5000.jpg
and you use
console>>>jobb -pn my.package.name -pv VERSIONCODE -d ./data -k obb_password
-o main.VERSIONCODE.my.package.name.obb
you will get the mentioned error. Try to add one directory-hierarchy and make the "data"-directory to a subfolder
- root/data/1.jpg
- root/data/2.jpg
- root/data/3.jpg
- root/data/...
- root/data/5000.jpg
use
console>>>jobb -pn my.package.name -pv VERSIONCODE -d ./root -k obb_password
-o main.VERSIONCODE.my.package.name.obb
you have to keep in mind, that if you want to read from the obb later, that the pictures are now in a subfolder.
Solution 2:
In addition to what Ix222 said about FAT16 limiting the number of files in the root directory, there's also an issue in the jobb tool itself, and the FAT library it uses.
In the FAT library it is determining the maximum filesystem size for FAT12 to be 4 MB, FAT16 at 512 MB and using FAT32 for anything beyond that. In reality FAT12 allows up to 16 MB (32 MB in some implementations) and FAT16 allows up to 2 GB. This is the reason that if your OBB size using the current tool is limited to the range 4 MB <= OBB size < 512 MB.
The jobb tool is also wrongly relying on the FAT library to determine the filesystem, but it is only compatible with FAT16.
A quick fix is to build your own version of the jobb tool (I recommend backing up the existing JAR and replacing it with your own, the Windows Batch file should still be used to run it) with a modified version of the libfat32 library built in. Simply modifying the method that determines the filesystem to return FAT16 for anything up to 2 GB and FAT32 otherwise is sufficient to build valid OBB files up to 2 GB (which is the limit for OBB files anyway).
SuperFloppyFormatter returning FAT32 for anything over 512 MB?
Solution 3:
I was getting the same behaviour but this was only in a test directory structure I was experimenting with. It had almost no content so maybe this is an issue with jobb at these small sizes. Or maybe some error conditions are met depending on the space taken up by the all the files. I've commented in more detail on the Google Code issue.
I wonder if adding a couple of redundant files might avoid this error behaviour for those that are experiencing it with non-trivial directory structures.
Solution 4:
Got the same problem and the workaround I found is to make an archive with a minimum size of 4mo. To add fake data to my small archive make it worked…
Solution 5:
In my case, I solved the issue removing several hidden files...
My boss owns and works on MacOSX, me on Windows. So, when he passed it on and after opening the folder, I found several hidden files, such as .DS_Store and ._.DS_Store. Additionally, I found hidden temporary JPGs, for example if I had a file called image1.jpg I had another one .image1.jpg. So, eventually I deleted all of the hidden files.
And voilà!
Post a Comment for "Using Jobb Tool In Android"