[chrialex]

Yes, at 65% used an 800 will have more free RAM than a 500, but it is still only 35% free. If you look at the MB's instead of the %, you should notice that if it wasn't working at, say 150MB (just for an example) used on a 500, but it works just fine at 200MB (again, just an example) used on an 800, there is something there. If Android was saying "I can't start when the device has only 50MB or 35% RAM free" then it should be consistent regardless of device, correct? It sounds like that is what your device is doing though, reading 65% used and giving an error to haret or something else along those lines. Regardless of if you two get along or not, something is going on with your device, so lets figure it out and see if it is actually Android or not. If it is, it would probably be good for the devs to know. If not, it would probably still be good for people to know in case someone else runs into it later on.

By the way, what version of SPB MS are you running, 3.5.5 is the newest one. I used to run that as well but it took too long with the dual booting of WinMo/MS and Android, so I stopped. A release or two back they did fix some memory leaks if I remember right. When you are in Android, what is your RAM usage after you kill everything normally? And how does that compare to WinMo? If it is better, and/or you can, try uninstalling everything from WinMo that you can get by with using in Android instead and see if that helps with your initial RAM usage. (Not saying that your device was at fault for the Android booting, just a suggestion)