maemo.org Bugzilla – Bug 5550
"Not enough memory in target location" when receiving image from Nokia SU-1B using Bluetooth
Last modified: 2010-03-15 20:52:47 UTC
You need to
before you can comment on or make changes to this bug.
STEPS TO REPRODUCE THE PROBLEM:
With the Nokia SU-1B digital pen you can transfer your written notes as a gif
image to your phone using bluetooth.
When you do this you get the "save file" dialog on the Nokia N900, but no
matter were you try to save the image it always says: "Not enough memory in
You would expect to be able to save to image file normally. It works perfectly
on the N800 tablet or any other Symbian phone I tried.
All other Bluetooth file transfers to the N900 work perfectly and there is
plenty of memory available.
No matter were you try to save the image, there is always the message "Not
enough memory in target location", but that is not correct, there is enough
memory in all locations I tried.
EXTRA SOFTWARE INSTALLED:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:220.127.116.11)
Gecko/2009090216 Linux Mint/6 (Felicia) Firefox/3.0.14
Thanks for reporting this.
Is the N900 supported/compatible with the SU-1B?
Could not find any info on http://europe.nokia.com/ and when it is not
officially supported it is not a bug...
According to the manual of the SU-1B it should support any phone that supports
"Object Push Profile", "Generic Object Exchange Profile", "Serial Port Profile"
and "Dial up networking profile".
I believe that the functionality that I'm talking about only involves the first
two profile (Object Push Profile and Generic Object Exchange Profile).
According to the user guide of the N900 that was on the Nokia US website some
time ago, the N900 should support these two profiles (page 33).
After (successful) pairing with the pen,
you check the send box on the paper
and the operation is started.
after a few moments you get a message on the N900:
Title: "Receive file"
"Receive file via Bluetooth?"
"Device: Nokia SU-1B"
"Open file after saving"
you hit "Save"
Then you get:
Title: "Save file"
you hit "Save"
But instead of saving the file in the "Images" location, you get an error:
"Not enough memory in target location"
If you select a different location you get the same message.
> According to the manual of the SU-1B it should support any phone that supports
> "Object Push Profile", "Generic Object Exchange Profile", "Serial Port
> Profile" and "Dial up networking profile".
I don't know exactly how to interpret the "and" here, if it means "all four of
them" then this is an enhancement request and not a bug.
The first two items are supported by the N900.
From http://www.forum.nokia.com/devices/N900/ :
A2DP, AVRCP, FTP, HFP, HSP, OPP. (Thanks VDVsx!)
Quoting from the on-device documentation of the N900:
"The device is compliant with Bluetooth Specification 2.1 + EDR supporting the
following profiles: General Access Profile, File Transfer Profile, Object Push
Profile, Generic Object Exchange Profile, Headset Profile, Hands Free Profile,
Advanced Audio Distribution Profile, and Audio/Video Remote Control Profile."
does not list the N900.
Johan, can you maybe comment on this, please?
(In reply to comment #4)
> Johan, can you maybe comment on this, please?
Sounds pretty strange. Is the reporter able to send files over Object Push from
any other device to the N900? What about creating a file in one of the
locations using e.g. the notes application?
(In reply to comment #5)
> (In reply to comment #4)
> > Johan, can you maybe comment on this, please?
> Sounds pretty strange. Is the reporter able to send files over Object Push from
> any other device to the N900? What about creating a file in one of the
> locations using e.g. the notes application?
Yes, transfers from others devices (tested with Linux PC, N95 and nokia 5800)
work perfectly. It doesn't matter what location you choose, they work with
these devices, but all locations I tested don't work with the SU-1B.
Just speculating here but could it be that none of those other devices provide
a length header in their Put request (it's optional in OBEX) whereas the SU-1B
provides it and there's a bug somewhere in the checks for this length header
(where it's compared to the actual available space).
Could you take a HCI level trace so we'd see if this is indeed the case. You
can do that by installing the bluez-hcidump package and running "hcidump -XV"
as root while trying to do the transfer. You can find the package e.g. here:
Be sure to start hcidump before you establish any connection since that way it
can determine that the higher level protocol is OBEX and will give you nice
human readable decoding of the OBEX headsers.
I tried to test it
I used the command: "hcidump -XV -w /home/user/MyDocs/su1b_dump.txt"
to create the log/dump file, but that doesn't seem to be a readable format.
So I used: "hcidump -XV > /home/user/MyDocs/su1b.txt"
To create the other log file.
it ends with "Reason: Remote User Terminated Connection", that is when you tap
outside the screen to cancel the transfer after you received the "Not enough
memory in target location" error
Created an attachment (id=1616) [details]
second hcidump file when a file is transfered from the SU-1B
Created an attachment (id=1617) [details]
the hcidump file when a file is transfered from the SU-1B
Imported (see Alias).
I'd like to confirm this one, but the other device in my case was a SE Z610
phone. I was attempting to transfer my entire set of contacts as a single
vcard, and I got the quoted error message on the N900.
There was plenty of space in all file-systems. I changed the location of the
bt download to a variety of places on different media and the problem
I get the exact same error condition trying to send any contact vcf from an old
Windows Mobile 2003 SE phone via bluetooth. The N900 recognizes the vcf file
and asks where to save it. Regardless of the location chosen, I always get the
not-enough-memory message and the only way to get out of the dialogs is to
cancel the transfer.
I get the same error too.
I am trying to send all my contacts from my Sony E// w700 to N900.
*** This bug has been confirmed by popular vote. ***
"Problem is that OBJECT_SIZE_UNKNOWN (-1) gets compared against free space of
the device which is of type GnomeVFSFileSize (guint64) and -1 is interpreted as
biggest possible guint64 -> not enough space"
This is being worked on.
I re-tested this after the 1.1 upgrade, and it appears to have been fixed in
I have successfully imported a full .vcf file through Bluetooth.
Also see 6705 which seems to be the same problem. I'll make a comment there
I also retested it using the Nokia SU-1B on the 1.2009.51-1 firmware, but I
still get the same result.
This has been fixed in package
which is part of the internal build version
(Note: 2009/2010 is the year, and the number after is the week.)
A future public update released with the year/week later than this internal
build version will include the fix. (This is not always already the next public
Please verify that this new version fixes the bug by marking this bug report as
VERIFIED after the public update has been released and if you have some time.
To answer popular followup questions:
* Nokia does not announce release dates of public updates in advance.
* There is currently no access to these internal, non-public build versions.
A Brainstorm proposal to change this exists at
Setting explicit PR1.2 milestone (so it's clearer in which public release the
fix will be available to users).
Sorry for the bugmail noise (you can filter on this message).