6 ms·
ArsTechnica unfortunately again misleads people due to limited expertise. On modern Androids (6.0+) accessing the microphone requires an explicit permission gr
by izacus 10y ago
ArsTechnica unfortunately again misleads people due to limited expertise.
On modern Androids (6.0+) accessing the microphone requires an explicit permission granted by user (just like on iOS).
Furthermore, due to Doze mode implemented in 6.0 and expanded in 7.0 running these kind of services without notifying the user cleary (with permanent notification) has become pretty much impossible and unreliable. To run in background when the phone isn't in active use the service needs to be marked "Foreground" which demands a permanent notification.
Having said that - Google is failing here in several ways. First, they STILL let apps be published that don't target Android 6.0. Apps that target older Androids get permissions granted at install time (those can be revoked, but user needs to go to settings for that). There's no reason to let people publish new apps that don't adhere to new permission model, but Google just doesn't care.
They also need to clearly mark use of system resources in the background - just like we have the GPS icon, we need a clear indication of active microphone, speaker and other hardware modules while running in the backgorund.
- macawfish 10y agoYes, I agree, including gyroscopes. As well as a way of seeing which apps are using the sensors.
- oneshot908 10y agoI would love love love if my Android phone would occasionally provide me a summary of which apps are making use of the camera, the GPS, and the microphone and allow me to disable them. Sure, I can hunt for this on my own. That's not the point here. If I'm walking around with a supercomputer in my pocket, I'd like it to do this sort of stuff for me automagically.
- izacus 10y agoSettings -> Apps -> Gear icon in the top bar -> App permissions should do what you want (at least it does on 7.1.2 / Pixel). Not obvious I know :/
- cwyers 10y agoNearly 2/3rds of Android phones that have accessed the Google Play store in the week leading up to May 2nd are not on Android 6 or later: https://developer.android.com/about/dashboards/index.html https://developer.android.com/about/dashboards/index.html
- izacus 10y agoI'm not sure what you're comment is trying to say - TARGETING a new API doesn't meant you don't SUPPORT an older API. It just determines backwards compatiblity behaviour. We currently release a product that supports Android 4.1 while targeting Android 7.1. Also this dashboard is hugely misleading for the HN audience - in western audiences (USA, Canada, EU, etc. - countries HN users are from) we're tracking ~10% devices that are running Android 4.x and more than 40% devices running on Android 6.0 with additional 15% on 7.x - meaning more than half of active western users are running decently modern Android.
- cwyers 10y agoWhat it's trying to say is that this can be a big problem even if it doesn't affect Android 6 and up. Your own statistics say it can affect up to 45% of Android users.
- izacus 10y agoI completely agree. The Android upgrade situation is a huge and rather well known issue.
- pjmlp 10y agoNot to Google, as they don't care. Now with Android N reaching 7%,one year later, who do they think will even bother with Android O?
- on_and_off 10y agoI work on a large Android app and we do bother with Android O. As soon as the sdk will be final we will think about compiling against it and targeting it. We are not in a huge hurry, it can skip a release or 2 (we release every 3 weeks). There are no big breaking changes though (unlike let's say Marshmallow) so as long as the support lib is stable (it needs to match with compile version) we are going to support it ASAP. We also have some N features like shortcuts.
- yehi 10y agoOne thing that Google really should do is allow a feature to temporarily give permissions or fake giving permissions. For example, I want to send my location on Whatsapp then I would want it to ask for permissions every time. Similar to how certain websites cannot access my microphone just because I let them do it once, neither should apps.
- anigbrowl 10y agoIf I understand you right, you're saying that this doesn't actually work most of the time - but not that people are not trying it. Myself, I don't care about the fact that Google is 'failing' on this, because even if they fix all the problems you identify, the people exploit such approaches will find some other loophole to exploit or work around. The inevitable result: another arms race that doesn't create value for consumers. What I care about is the recurring social problem of which this is just the latest instance: marketing/advertising folk deceiving consumers. If your business model relies on deception then you are a Bad Person, and this applies equally to those who dream up such schemes and those who implement them at the technical level. The legal system does not move at the speed of software development, and so there are strong economic incentives to engage in such unethical behavior and move on before people catch on and organize themselves to litigate the issue or effectively regulate the behavior. It is time, therefore, to punish bad actors by more direct methods of retaliation, which necessarily involves inhibiting their ability to buy their way out of trouble by renting legal mercenaries.