# deinit

Source: [https://docs.qualcomm.com/doc/80-PK177-134/topic/individual_subsystem_deinit_native.html](https://docs.qualcomm.com/doc/80-PK177-134/topic/individual_subsystem_deinit_native.html)

Invoked on the subsystem manager instance to de-initialize the framework.

    <Subsystemclass>.deinit() Copy to clipboard

For example:

    SensorsManager.deinit()Copy to clipboard

Note: 
        An activity/module of an application can continue to use the existing session with a
        feature/subsystem. For example, modem/performance/sensors/location even if other
        activities or modules of the application deinitialize the session with the same
        feature/subsystem. This allows applications to have different modules that use QESDK
        features independently without worrying about what other modules in the same
        application do with the same QESDK feature.

**Parent Topic:** [Initialize or de-initialize individual subsystems](https://docs.qualcomm.com/doc/80-PK177-134/topic/init_or_deinit_individual_subsystems_native.html)

Last Published: Nov 14, 2024

[Previous Topic
init](https://docs.qualcomm.com/bundle/publicresource/80-PK177-134/topics/individual_subsystem_init_native.md) [Next Topic
QESDK event callback](https://docs.qualcomm.com/bundle/publicresource/80-PK177-134/topics/native_fwk_event_callback.md)