reboot your phone and check for updates. you should be able to get it. it is around 80MB update so use wifi.

this is a bug fix update so don't expect too much. according to official change log it brought ovi suite support.

Simple gogle search will give you the download link 

http://www.google.co.uk/search?q=RX-51_2009SE_20.2010.36-2_PR_COMBINED_MR0_ARM.zip

It is week 36 build 2

File name: RX-51_2009SE_20.2010.36-2_PR_COMBINED_MR0_ARM.zip

MD5: b9f8690318a3be61767826d15b8c1784

SHA1: 54c9e5d6491ea73f9f4131c9f19cc01f9934fcdb

If you haven't, read Another Simple C# Wrapper For FFmpeg before this post.

After long hours of suffering I found a solution to large video encoding on asp.net with ffmpeg! If you ever tried you already know that encoding videos larger than 5-6 MB with asp.net and FFmpeg couses Application pool to hang and start eating froms erver's ram. I finally found out that you  .NET does not provide more memory to FFMpeg. When converting large files, FFMpeg's out put stream gets filled and waits for .NET to allocate memory resources but is never done. In order to utilize less memory, you need to the buffer periodically.

To do that, just add below method to Encoder.cs and use it in EncodeVideo method instead of using RunProccess method. Or, you could replace actual RunProccess method with this one.

private string RunProcessLargeFile(string Parameters)
        {
            /* The below will be the right solution ....
             * The while loop which reads the stream is very improtant 
             * for FFMPEG as .NET does not provide more memory to FFMPEG. 
             * When converting large files, FFMPEG's out put stream gets filled...
             * And waits for .NET to allocate memory resources but is never done. 
             * In order to utilize less memory, we are clearing the buffer periodically.
             **/

            ProcessStartInfo oInfo = new ProcessStartInfo(this.FFmpegPath, Parameters);
            oInfo.WorkingDirectory = Path.GetDirectoryName(this.FFmpegPath);
            oInfo.UseShellExecute = false;
            oInfo.CreateNoWindow = true;
            oInfo.RedirectStandardOutput = true;
            oInfo.RedirectStandardError = true; 
            using (Process proc = System.Diagnostics.Process.Start(oInfo))
            {
                using (StreamReader srOutput = proc.StandardError)
                {
                    System.Text.StringBuilder output = new System.Text.StringBuilder();

                    using (StreamReader objStreamReader = proc.StandardError)
                    {
                        System.Text.StringBuilder sbOutPut = new StringBuilder();

                        while (!proc.WaitForExit(1000))
                        {
                            sbOutPut.Append(objStreamReader.ReadToEnd().ToString());
                        }

                        if (proc.ExitCode == 0)
                        {
                            proc.Close();
                            if (objStreamReader != null)
                            {
                                objStreamReader.Close();
                            }
                        }
                        else
                        {
                            proc.Close();
                            if (objStreamReader != null)
                            {
                                objStreamReader.Close();
                            }
                        }
                        return sbOutPut.ToString();
                    }
                }
            }

        }

I've been having few problems with my Asp.net downloader (see http://nolovelust.com/post/C-file-downloader-AKA-ResponseBinaryWrite.aspx). Problem was that if I start to download a file Asp.net would not respond to other requests from same session. After a bit of research I've came accross http://forums.asp.net/t/1204045.aspx and http://www.guidanceshare.com/wiki/ASP.NET_2.0_Performance_Guidelines_-_Session_State

So by adding EnableSessionState="ReadOnly" to my page i was able to get Aps.net to respond subsequent requests