>
New Topic
>
Reply<
Esato Forum Index
>
Sony Ericsson / Sony >
General
> Problem of storing pictures in T68i and T300
Bookmark topic
Confirmed, my T68i, which is R2E006, also exhibits the grown filesize problem. It seems to be independent from the source of the image as some of my images where transferred from an irDA port while others were downloaded via WAP...
Very strange indeed...
--
Posted: 2002-10-21 03:06:00
Edit :
Quote
So is this a bug or that just the way sony ericsson phones allocate the memory size??? Should we report such problem to sony ericsson??? Because we would have been able to store far more backgrounds and themes etc if the phone actually take up the file's actual size instead of twice or three times than the actual size !!
--
Posted: 2002-10-21 09:52:00
Edit :
Quote
The size that u see in PICTURE INFO is the actual size of the picture while the size that you see in MEMORY STATUS is the size of memory consumed (size on disk) when it was saved. It has something to do wìth the file compresion format of the program that is being used. It is also the same in any Windows OS. Click properties on any windows file and you'll see that the actual file SIZE is different (smaller) from the SIZE ON DISK (larger).
This post was posted from a T68i
--
Posted: 2002-10-21 10:19:00
Edit :
Quote
It's because of the compression GiF files use. they use LZW compression. Thats the only difference between a gif file and a bmp. notice how much bigger bmp files are? I beleive what the T68i does is it uncompresses the gif file once it is saved, therefore doubling the size or more. I beleive this is done to save the processor power on the T68i. they sacrifice memory for speed and battery life. Not sure if any software upgrade can fix this....
Quote:
On 2002-10-21 10:19, mkphil wrote:
The size that u see in PICTURE INFO is the actual size of the picture while the size that you see in MEMORY STATUS is the size of memory consumed (size on disk) when it was saved. It has something to do wìth the file compresion format of the program that is being used. It is also the same in any Windows OS. Click properties on any windows file and you'll see that the actual file SIZE is different (smaller) from the SIZE ON DISK (larger).
This post was posted from a T68i
--
Posted: 2002-10-21 10:23:00
Edit :
Quote
One thing that bothers me is why the THM size on disk is the same as the actual file size? Is it that these files are as is and doesn't need compression or decompression? It is also the same with the IMY/EMY files. If so, I think SE should make a picture file type of its own that will not need de/compression;-)
This post was posted from a T68i
--
Posted: 2002-10-21 10:47:00
Edit :
Quote
it's not the case with .imy or .emy files because those are just ascii text where as .gif is an LZW compressed binary bitmap. A faster processor would fix the problem.
Quote:
On 2002-10-21 10:47, mkphil wrote:
One thing that bothers me is why the THM size on disk is the same as the actual file size? Is it that these files are as is and doesn't need compression or decompression? It is also the same with the IMY/EMY files. If so, I think SE should make a picture file type of its own that will not need de/compression;-)
This post was posted from a T68i
--
Posted: 2002-10-21 12:23:00
Edit :
Quote
So what can we do ??? Or it just the way it is ??
--
Posted: 2002-10-21 12:28:00
Edit :
Quote
Yes, its just as it is for now. The least SE could do is update the software so decompression will be less as it used to be.
This post was posted from a T68i
--
Posted: 2002-10-21 13:04:00
Edit :
Quote
I hope P800 aren't like this !!!!
--
Posted: 2002-10-21 13:25:00
Edit :
Quote
Maybe you have a software defect. My first T68 had an undetectable SW defect discovered when I took it to SE for upgrading. They replaced my board with a new 1. Have yours checked by your sp.;-)
This post was posted from a T68i
--
Posted: 2002-10-21 14:03:00
Edit :
Quote
New Topic
Reply
