Anonymous sit down and shut up, stop wasting people's precious time
You should take your own advice, really. It not only stupid but utterly ridiculous to, despite numerous calls not to, screw with system files and then request support and post "what would be ideal' comment.
[deleted] I did read those posts. I did trust the GOS developers enough to flash their software. I trust no one, completely, and neither should anyone else. I obsessive, compulsively research, ask questions, even the 'stupid' ones, sometimes make mistakes and learn from them so I can trust myself... reasonably. If we all blindly, mindlessly, naively trusted, we'd all still be content with Google unchecked. Additionally, would the developers have provided the option and instructions for anyone to build their own GOS if they intended we not touch system components?
f13a-6c3a Did you inspect that inane babble before posting? I did not 'screw with system files' and then request support. And ideal, is an environment of free will and choice. It would be fantastic if humanity were allowed to evolve. Though, I doubt communists would agree with that sentiment.
What's so offensive about freedom with recommended guidelines?
Anonymous just to remind you, sensor permission is a GOS own invented permission and as such it mostly regards to control over user installed (not system) apps. If you were using usual stock Android, you would have absolutely no control over it. So please don't touch system apps, focus on the ones you choose to install.
It has occurred to me that, perhaps, the people commenting aren't aware of the relevance associated with the OP's question, since we've gone so off topic with how thing should or shouldn't be, what people should or shouldn't do with their personal property, etc.
Follow along if you want to understand "Lots of F-Droid apps have sensor access by default. Is this required?"
Settings/Privacy/Permission manager/Sensors.... behold, literally, every app, all 131, prior to selecting "Show system," are "Allowed." When you select "Show system," there are an additional 26 apps for which the option to decide whether to "Allow" or "Don't allow," is disabled, so the discourse on touching "System" apps is moot. I believe the misunderstanding is surrounding the confusion between the terms used; "User," "System" and "User installed" apps. When I was initially setting up my phone, I wondered why all 131 "User" apps had access to "Sensors" by default, and I believe this was what motivated undwersq's question in the first place, (correct me if I'm wrong.) To anyone whom knows their way around an Android phone, it is unusual and , therefore, a valid question.
In the future, for clarity sake, for new users whom may have the same questions:
At this point in time, there are 131 "User" apps and 26 "System" apps for a total of 157 apps that come preinstalled as part of Graphene OS. These apps do not have "Sensors" permissions on stock Android, this is a permission unique to GrapheneOS. All of these apps come with "Sensors" permission "Allowed" by default in order to avoid breaking them due to not knowing how they will function without the permission, which seems counterintuitive considering they never even had the permission in the past? You have the ability to toggle "Don't allow" on all 131 "User" apps, but not on the 26 "System" apps. It is unclear if toggling "Don't allow" on the 131 "User" apps will cause system or app specific dysfunction. You can, of course, choose "Allow" or "Don't allow" on any app that you install independent of preinstalled apps, "User installed" apps. If you go to "Settings" and then "Privacy," scroll down to "Allow Sensors permission to apps by default" and toggle it off to deny this default permission to "User installed" apps, but the change only applies to apps installed after it has been toggled off. If you installed apps prior to discovering this feature, and wish to change their access to "Sensors" permission, it will have to be done manually, either by going to "Settings" then "Apps," or "Settings then "Privacy" and then "Permission manager."
According to Google Pixel support, "Sensors" are as follows:
Pixel 4 and 5:
Proximity/Ambient light sensor
Accelerometer/Gyrometer
Magnetometer
Pixel Imprint™ – back-mounted fingerprint sensor for fast unlocking
Barometer
Spectral and flicker sensor
Pixel 6-7:
Ambient light sensor
Accelerometer
Gyrometer
Magnetometer
Barometer
Proximity sensor
Pixel Fold:
Same as 6 and 7
Hall effect
Is this correct? Also, if one were to toggle off any of the 131 preinstalled "User" apps, and an app needed the permission to function, do we know if the app will break, malfunction or ask for the permission to be enabled?
Anonymous These apps do not have "Sensors" permissions on stock Android, this is a permission unique to GrapheneOS. All of these apps come with "Sensors" permission "Allowed" by default in order to avoid breaking them due to not knowing how they will function without the permission, which seems counterintuitive considering they never even had the permission in the past?
See, access to sensors is FULLY ALLOWED for ALL apps on Android. GrapheneOS has its own runtime permission for Sensors, which is allowed by default to avoid breaking comatibility. The GrapheneOS Official Project account has already stated that Removing the sensors permission from components in the OS not requiring it would be internal OS hardening work with very low impact. : GrapheneOS
[deleted] Sorry, I don't understand what you mean by "see access to sensors is FULLY ALLOWED for ALL apps on Android"... where can I see that? Based on the statement that I can see here, ("Removing the sensors permission from components in the OS not requiring it would be internal OS hardening work with very low impact"), it sounds like they are saying you can do it, but it may not be worth the effort?
Anonymous What I believe they were trying to say is that on Android (not GrapheneOS), all apps, including system apps have access to the sensors gated by the sensors permission on GrapheneOS by default. It is GrapheneOS that adds the option to disable that permission, it doesn't exist on Android at all.
On GrapheneOS, you can revoke the sensors permission, though for the reasons mentioned above, it's not a good idea as you're more likely to mess something up and the gain is minimal at best.
As for what was mentioned by the project account, it might make sense for the project to revoke sensors from system apps that don't need it, but it likely wouldn't be worth the effort as you say, especially since it will requite actively maintaining that going forward (a system app that previously didn't require sensors access now does and vice versa).
On that note, I believe the inquiries in this thread have been addressed and I will be marking the thread as solved. Furthermore, this is a general reminder/warning to everyone:
It is unavoidable that we will sometimes get heated when interacting with others online or in real life. Let's not let our first instinct to be to give in to that and to start or participate in arguments. It degrades the experience for everyone. This isn't a real-time chat; you have time to think about your reply before posting it. This should be leading to less arguments compared to a real-time chat where things can get out of hand, not less. Let's make sure to adhere to that going forward, which will be a positive change for everyone (participants and future members reading through old threads alike).
I absolutely hate having to tell grown adults to adjust their tone - it truly feels like I'm talking down to y'all, so please rest assured that it's not something that's fun for me, but if we continue to have arguments on here, we'll have to do that as well as proceed with temporary or even permanent suspensions in extreme cases.
To be clear, this isn't directed to any one individual, but is rather a general note.
Thank you all for your understanding.
Anonymous You are thinking that System Apps for some reason are having the Sensors permission on GrapheneOS, but not on Android. The Sensors permission does not even exist on Android, so apps don't need any permission for accessing the Sensors (not Body sensors).
Anonymous Based on the statement that I can see here, ("Removing the sensors permission from components in the OS not requiring it would be internal OS hardening work with very low impact"), it sounds like they are saying you can do it, but it may not be worth the effort?
Yes, They are saying that removing the Sensors permission for System apps that don't require it by default would be very low impact, and that It would be a maintainance burden. You should just read the whole post: https://discuss.grapheneos.org/d/6310-why-so-many-apps-need-sensor-access/13
matchboxbananasynergy Sorry, I was writing my post and and didn't notice you've posted this. I'll refrain from further discussion here.
[deleted] Thanks for the link, much appreciated! Oh, I see, yes, I saw that as is evidenced by the last post I made in an attempt to make sure that I understood, accurately, what had been explained previously. I guess I got it right since it's been tagged as solved. It may be the way my particular brain is wired, but I find a lot of the verbiage challenging to digest. I really appreciate the patience and time taken to help! Cheers!
Before this post I didn't even know what these sensors are, and what are they for...
