Not sure if this is just Android behavior or not with services. But onDestroy does get called and I'm pretty sure I'm disposing of every object properly. Regardless, this is causing us to leak a little bit of memory each time this happens. After 40+ open/close cycles in rapid succession it starts to affect system performance.
Force stopping the Kaku service through Android's Apps screen / service screen will reclaim lost memory and return performance back to normal on the device though.
Not sure if this is just Android behavior or not with services. But onDestroy does get called and I'm pretty sure I'm disposing of every object properly. Regardless, this is causing us to leak a little bit of memory each time this happens. After 40+ open/close cycles in rapid succession it starts to affect system performance.
Force stopping the Kaku service through Android's Apps screen / service screen will reclaim lost memory and return performance back to normal on the device though.