SweeterHome

I think these have all been memory management tweaks, as far as I can tell.

Still get the acore error on boot. I've heard of other roms having this problem as well, so I'm not sure it's a Sweeterhome issue. Got everything loaded up and testing. Seems like images are more stable - I was able to add them to an already overloaded theme and it lags a little. Might try stepping up to a 1200 kernel, but that's liable to cause redraws and soft FC's.

Editing lags really bad with the images added, but it doesn't crash like it would before. Seems to be running pretty stable and solid, so I think we are looking at being pretty close to a public release

Currently running Sapphire 0.6 with Chevy's ULV 1000 and no theme. Seems like I'm still getting some slowwwwww re-draws (again, probably a Froyo/rom issue) and the occasional soft close, but will report later. Maybe tomorrow I'll load up my theme again including the images (just a work around I have to show wallpaper over underlying layers on each "screen" since technically it's locked on 1 screen)

I'll try and let you guys know when there are feature additions. Until then, just assume all changes are memory/bug related as the dev moves forward towards stability.

Thanks for the follow up, Lemon.

Please understand, I'm not trying to be a jerk about this, I just really want to help you guys find and solve problems and issues as effectively as possible, since I really believe this to be one of the greatest developments for Android to date.

I spend a lot of time working with software devs and managing beta software testers in my day job, so I've got experience with how to get the best feedback out of folks, something that's particularly difficult when everybody is just doing it in their spare time and can be a bit myopic in their testing (such as I am being by sticking with the Froyo ROM I've been using, to be honest).

As I've mentioned before, if there is anything you want us to try, test or help out with, just ask. For my part, I'm happy to help however I can.

Sweet bro! The best thing you can do is log reports when ever anything goes a bit haywire. If a crash/report dialog pops up then report it, otherwise you can grab a logcat or ddms log and email to bugs(at)sweeterhhome(dot)com, with a description of the exact issue.