The FLV playback on N95 and N96 stops after this "NetStream.Buffer.Empty" status message is received. Can anyone from Nokia or adobe clarify if it is a Flashlite bug on these phones. It works properly on N86.
The FLV playback on N95 and N96 stops after this "NetStream.Buffer.Empty" status message is received. Can anyone from Nokia or adobe clarify if it is a Flashlite bug on these phones. It works properly on N86.
Why dont u dump the old thread. However, just let us know one thing that whether same amount of ram is free on both of these devices (N86 & N95)? You can check the amount of ram by using Y-tasks. It may help us to know whether it is a software related issue or not.
Best Regards,
SajiSoft
I don't know if it is a similar issue, but when I play 7-8 flv files continously on N86, it gives not enough memory error. I ma using the following code-
var connection:NetConnection;
var stream:NetStream;
connection = new NetConnection();
connection.connect(null);
stream = new NetStream(connection);
video.attachVideo(stream);
stream.play(file);
when the playback of one file is over, I call the following code to clean up before starting a new stream-
video.clear();
stream.close();
Is there any problem in the code? Why is the heap not getting cleaned up?
Regards
Ramesh
You can track the heap memory in Device Central (2mb is the default amount of heap memory allowed to Flash Stub in device) or by issuing a fscommand2("GetFreePlayerMemory").I recommend u to read this article :
Memory Management
Moreover, u can increase the heap memory for ur Flash stub. Read here :
Symbian C++ Stub For Flash Lite
Wish u luck..
Best Regards,
SajiSoft
Hi ramesh130,
the buffer starts to replenish once emptied and it might take some time to fill till the buffer length that you must have stipulated for your net stream object.
e.g.
var x:Number = <some_numeric_value>;
stream.setBufferTime(x);
Hence until the stream.bufferLength reaches the value 'x' the stream will not begin again. I am not sure if this is specifically some problem with the mentioned handsets, but you could also try the above method and have some dynamic text mention the value of stream.bufferLength while you run the application on your handset.
Regards,
Supriya Tenany
Hi,
I have tried all that. Only thing works is bandwidth throttling. Its not a buffer underrun issue as i can trace all the packets are getting tranferred to the app.
Ramesh