3 ms·
And/or an Android phone, apparently.
by angelbob 11y ago
And/or an Android phone, apparently.
- mindslight 11y agoIf Android apps can use the microphone without a clear indication, especially in the background, then that is a serious security bug in Android and should be reported with that context and fixed, rather than weird nobody's-fault alarmism.
- rdancer 11y agoWelcome to Android, hope you'll enjoy the stay.
- pilsetnieks 11y agoThat's what you get with a permission model of "hey, if you don't like that this app asks for every permission known to man, just don't use it!"
- mindslight 11y agoWell no. I purposely avoided getting into that territory, even though I have strong feelings probably similar to yours. Even with the take-it-or-leave-it faux-contract of adhesion permission model, there should be a visual indication when an app is using the microphone. Background microphone (not as a result of a directly preceding user intent) should be a separate additional permission, and probably shouldn't be exempted from having a visual notification with an easy way to mute the passive listening.
- lovelearning 11y agoIn Android, it's super simple for an ads framework or a malicious framework - installed as part of some useful app - to run a background service and keep recording microphone and phone calls. It is possible to hack the Android platform or OS to prevent or mitigate mischief like that, but ironically, it requires devices to be rooted. Android architecture rewards the bad guys by obstructing the good guys! I think mass migration of all devices to something like Cyanogenmod is the only solution.
- _delirium 11y agoSince Google's own "Google App" listens in the background without a clear indication, I doubt Android will be fixed on that point.