Why does Weather Master require so many system hooks and observers? · Issue #400 · PranshulGG/WeatherMaster · GitHub
More Web Proxy on the site http://driver.im/
You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I recently analyzed the behavior of the Weather Master app and noticed it's registering for a large number of Android system broadcasts and content observers that seem unrelated to standard weather functionality.
These seem excessive for a weather app, especially considering the sensitivity of some hooks (USB attachment, trust store changes, keychain events, etc.).
Questions:
Are these used for legitimate functionality, or were they included unintentionally?
Is there a plan to reduce unnecessary hooks for privacy-conscious users?
Can you clarify if any of these are dependencies of a library or analytics SDK?
The text was updated successfully, but these errors were encountered:
I recently analyzed the behavior of the Weather Master app and noticed it's registering for a large number of Android system broadcasts and content observers that seem unrelated to standard weather functionality.
Observed Broadcast/Event Hooks
android.hardware.usb.action.USB_DEVICE_ATTACHED
android.hardware.usb.action.USB_DEVICE_DETACHED
android.intent.action.HEADSET_PLUG
android.intent.action.LOCALE_CHANGED
android.intent.action.PROXY_CHANGE
android.intent.action.TIMEZONE_CHANGED
android.security.action.KEYCHAIN_CHANGED
android.security.action.KEY_ACCESS_CHANGED
android.security.action.TRUST_STORE_CHANGED
com.example.weathermaster.GPU_PROFILER_START
com.example.weathermaster.GPU_PROFILER_STOP
Invoked Methods
android.media.AudioManager.getOutputLatency
android.os.Trace.asyncTraceBegin
android.os.Trace.asyncTraceEnd
android.os.Trace.isTagEnabled
android.os.Trace.traceCounter
android.security.net.config.RootTrustManager.checkServerTrusted
android.security.net.config.RootTrustManager.isSameTrustConfiguration
android.view.textclassifier.logging.SmartSelectionEventTracker.logEvent
com.example.weathermaster.MainActivity$1.onHideCustomView
com.example.weathermaster.MainActivity$1.onShowCustomView
Content Observers Registered
content://settings/global/animator_duration_scale
content://settings/secure/accessibility_captioning_background_color
content://settings/secure/accessibility_captioning_edge_color
content://settings/secure/accessibility_captioning_edge_type
content://settings/secure/accessibility_captioning_enabled
content://settings/secure/accessibility_captioning_font_scale
content://settings/secure/accessibility_captioning_foreground_color
content://settings/secure/accessibility_captioning_locale
content://settings/secure/accessibility_captioning_preset
content://settings/secure/accessibility_captioning_typeface
content://settings/secure/accessibility_captioning_window_color
These seem excessive for a weather app, especially considering the sensitivity of some hooks (USB attachment, trust store changes, keychain events, etc.).
Questions:
The text was updated successfully, but these errors were encountered: