Ticket #71 (assigned defect)

Opened 10 months ago

Last modified 5 months ago

Failed to save track

Reported by: marcert Assigned to: saua (accepted)
Priority: major Milestone: 1.0
Component: MIDlet Version: 0.5.1
Keywords: Cc:

Description

Hi, unfortunately it is not every time possible for me to save the track because after "Stop track" I get the following exception: javax.microedition.rms.RecordStoreFullException? No track directory set

I get this although I configured a track directory: SDCard/Blackberry/ Even after modifying this directory I got the message "No track directory has been selected"

This is on a Blackberry 8310.

Change History

02/06/08 10:24:39 changed by saua

  • status changed from new to assigned.

The RecordStoreFullException? is caused when the record store is full (you probably thought as much). I'm using the record store as a fallback storage, when the track directory is not configured or can not be written to. It is usually of very limited capacity, so it will fail after a few tracks. That's expected and I can't really do anything about it.

The root cause of your problem, 'though, seems to be that the track directory you configure is not used or not recognized.

Could you tell me how you configured that directory? Did you write the name in yourself or did you select "Browse"?

02/06/08 11:09:25 changed by marcert

Hi, I used the Browse to navigate to the directory. I tried the built-in memory as well as the SD Card (which is 512MB and empty). It looks that the configuration of the path doesn't work because independent of the selected path I got the message "No Track directory has been selected"

Thanks Marco

06/10/08 10:16:10 changed by rossi

I experienced the same problem. My mistake was that i connected the phone to the PC before stoping the recording. Unfortunately this caused the phone itself to loos filesystem access to the SD-card. You can not even set the SD card as the track directory while the phone is connected to the pc because it is simply not visible in the directory browser. But this is a problem of the BB OS.