Froyo update and Quickoffice

mds0001

New member
Dec 2, 2010
4
1
0
So I finally got around to installing the official Froyo update. Have worked through most technical difficulties, but cannot figure out this one:

I use Quickoffice to view and edit Word docs and Excel spreadsheets. After the update to 2.2, I am still able to edit spreadsheets, but if I change a cell that is part of a calculation, I get an error message ("Not enough memory to finish recalculation"). None of the calculations will update.

Quickoffice customer support has given me inconsistent feedback that boils down to "please buy our paid version for $15." I am not inclined to do so in the first place, but particularly not when their free version is generating an error that they cannot explain. First they said that the update changed the installed version of Quickoffice to a view-only version (not the case -- the version has not changed since the update and the new program allows editing and saving; it just won't recalculate the spreadsheet). When I pointed out that was nonsense, they said that the new firmware had caused the features of Quickoffice to be "cut down" and the issue could only be solved by a firmware fix from Samsung (or by buying their paid program).

Has anyone (a) experienced and resolved this problem or (b) successfully used Quickoffice to edit a spreadsheet with calculations in it under Froyo? I have seen other threads relating to a different Quickoffice problem under Froyo (application shows grayed out/"read only") which was solved with a factory reset of the device, but I'd rather not go down this road if I have a different problem that it is not going to solve.

Thanks!
 
OK, I have to recant my skepticism about the "version change" story. I went back and looked at my backup of the application prior to the firmware update, and it was version 3.3.4, rather than new version 3.3.51. I reinstalled the backup copy of the apk, and presto it works again. Apparently version 3.3.51 is either buggy or intentionally crippled (though it was certainly not "read-only"!).