Error when copying to File.DirDefaultExternal

[CidTek]

I get an error when installing a file to SD storage executing this line. It worked since day one and now it just pops the error in the screenshot.

File.Copy(File.DirAssets,"grt.db",File.DirDefaultExternal,"grt.db")

 

[Erel]

You can check LogCat (in the right pane) and see if there is any more information.

 

[CidTek]

You can check LogCat (in the right pane) and see if there is any more information.

How do you select and copy text in the LogCat pane? All I can do is highlight one line at a time.

 

[Erel]

You will need to take a screenshot for now.

 

[CidTek]

You will need to take a screenshot for now.

Perhaps this is the problem. I found this entry when I unchecked Filter.

Data exceeds UNCOMPRESS_DATA_MAX (7897088 vs 1048576)

Does the emulator has a size restriction per application because it is well below the 16 meg size of the emulator SD?

 

[agraham]

Look at this link for the reason for the error Dealing with Asset Compression in Android Apps.

"any compressed asset file with an uncompressed size of over 1 MB cannot be read from the APK."

and a possible workaround

"rename your file’s extension"

 

[CidTek]

Look at this link for the reason for the error Dealing with Asset Compression in Android Apps.

"any compressed asset file with an uncompressed size of over 1 MB cannot be read from the APK."

and a possible workaround

"rename your file’s extension"

That got me past the original error, now I get a "No space left on device error".

My SQLite file is 7712 KB.

 

[CidTek]

OK, I restarted the emulator and wiped user data as an startup option.

Running the app I now get a new error "Disk I/O Error" on this line...

SQL1.Initialize(File.DirDefaultExternal, "grt.jet", False)

Note that I renamed my db file with a .jet extension to prevent compression as suggested above.

 

[Erel]

It might be an "emulator only" problem. It is worth checking it on a real device.

 

[CidTek]

It might be an "emulator only" problem. It is worth checking it on a real device.

Problem solved.

This applies only to SQLite databases created before uploading to the phone. Not to databases created on the phone.

For some reason Android requires every database to have a table called android_metadata that includes at least one locale.

Using your own SQLite database in Android applications | ReignDesign Blog

However there is a better solution which Basic4Android doesn't support as far as I can see and that is to use the SQLiteDatabase.NO_LOCALIZED_COLLATORS flag when opening the database.

 

[nfordbscndrd]

That fix was also mentioned at in another thread, but the error I was getting was that the only table in my database was "not found". Strange that it was giving you different errors. I guess that the moral is that everyone putting an existing database on a device needs to make sure they have done the fix first.

 

[CidTek]

That fix was also mentioned at in another thread, but the error I was getting was that the only table in my database was "not found". Strange that it was giving you different errors. I guess that the moral is that everyone putting an existing database on a device needs to make sure they have done the fix first.

I found that adding the android_metadata table is all I needed to do and didn't bother with the instructions to rename the primary key field in all the other tables.

However there are plenty of mentions out there that passing SQLiteDatabase.NO_LOCALIZED_COLLATORS flag when initializing the database eliminates that hassle. I just wish that B4A supported that.

 

[Erel]

However there are plenty of mentions out there that passing SQLiteDatabase.NO_LOCALIZED_COLLATORS flag when initilizing the database eliminates that hassle. I just wish that B4A supported that.

Will be fixed for the next update.

 

[Erel]

The attached SQL library sets the NO_LOCALIZED_COLLATORS flag. Please try it and see if it fixes the problem.

 

[CidTek]

The attached SQL library sets the NO_LOCALIZED_COLLATORS flag. Please try it and see if it fixes the problem.

Thanks Erel, I'll give it a test.

 

[CidTek]

Thanks Erel, I'll give it a test.

I removed the android_metadata table and tested the app and it works just fine.

Thanks again Erel, I am developing this transit app in tandem with a friend who is doing the iPhone version and it makes using a common SQLite db so much easier.

 

[nfordbscndrd]

Where do the files go?

 

[CidTek]

Where do the files go?

Program Files\Anywhere Software\Basic4Android\Libraries

 

[Erel]

You can also configure an "additional libraries path". It is set under Tools - Configure Paths.

 

[alfcen]

I guess that the moral is that everyone putting an existing database on a device needs to make sure they have done the fix first.

I have a database created with the SQLite Database Browser (CSV import).
After deployment to the phone, I copied the database file back to the PC and found that a table called "android_metadata" containing a field "locale" = en_US has been created automatically.

Apparently, not all phones or Android versions perform that step automatically, so I believe the modified library is neutral, thus safer (no such locale field added after switching to the new library).