Dam. I read the Intent API reference again and I dig out a method called setClass(). It really give me light of hope on making Mario stateless without using application to backing it! Lots to do. But I think it would ultimately solve all problems.

*Update*

Mario Coin Block Widget was updated to 1.3. With the setClass() function finding, I managed to set arbitrary lots of intent to drive the appwidgetprovider to work. So, even the application is killed (coz of low memory or task killer etc). It still managed to response to the remote view’s firing of the event.

Advertisements