Samsung Device Issue (Update/06/2011)

Getting there with the Samsung Devices.

Right....

• Galaxy S and Captivate devices work!
• Galaxy S2 and Infuse still don't!

So onwards, I have access to the Galaxy S2 browser code and can see that it is different to the Galaxy S structure and format. I will try and add this functionality to the application as soon as I have a spare moment.

On another note, I have released a PhoneMarks Development version (which is locked to only run for certain users). This is my testing/development platform for beta testing any updates without effecting the released products. I am using this with a SGS2 user to beta test the new update and check it works before I release it within the main application. If you are interested in becoming a beta tester or are having problems with PhoneMarks, then please email me your Google email address, phone/os details and your problem. I can then enable you to use this version and hence debug and fix your problems.

PhoneMarks 11.6.16 Released! (Android)

Minor update to stop ForceClose issuses on SGS2. I haven't solved the problem, just stopped the ForceClose and stopped using the new folder code.

PhoneMarks 11.6.9 Released! (Android)

Samsung devices now supported! Well almost.

I have had reports that Galaxy S and Captivate devices now work. The Galaxy S2 doesn't, it reports a ForceClose. Will investigate and try to add this to the supported list.

Please note: On these devices, only a single folder level is supported so the folder name is a combination of all the folder names combined.