android - Lifecycle of service deployed as separate APK -
i developed dummy service , test application uses - using bindservice. service , test app deployed separate apks.
after test app terminated (it unbinds service) service perspective see calls onunbind , ondestroy respectively. still service listed cached background process under settings -> apps -> running (show cached processes). test app not listed expected.
i thought android terminate application providing service when service unbound , destroyed? how terminate or standard android caching mechanism though destroyed?
i thought android terminate application providing service when service unbound , destroyed?
the service process behave no differently other sdk app's process. 1 time there no running components (in case, 1 time there no bound connections), process remain in memory until android needs memory other purpose. how process terminated hence depends on environmental conditions.
android service lifecycle
No comments:
Post a Comment