Android
The new home of /r/Android on Lemmy and the Fediverse!
Android news, reviews, tips, and discussions about rooting, tutorials, and apps.
🔗Universal Link: !android@lemdro.id
💡Content Philosophy:
Content which benefits the community (news, rumours, and discussions) is generally allowed and is valued over content which benefits only the individual (technical questions, help buying/selling, rants, self-promotion, etc.) which will be removed if it's in violation of the rules.
Support, technical, or app related questions belong in: !askandroid@lemdro.id
For fresh communities, lemmy apps, and instance updates: !lemdroid@lemdro.id
📰Our communities below
Rules
-
Stay on topic: All posts should be related to the Android OS or ecosystem.
-
No support questions, recommendation requests, rants, or bug reports: Posts must benefit the community rather than the individual. Please post to !askandroid@lemdro.id.
-
Describe images/videos, no memes: Please include a text description when sharing images or videos. Post memes to !androidmemes@lemdro.id.
-
No self-promotion spam: Active community members can post their apps if they answer any questions in the comments. Please do not post links to your own website, YouTube, blog content, or communities.
-
No reposts or rehosted content: Share only the original source of an article, unless it's not available in English or requires logging in (like Twitter). Avoid reposting the same topic from other sources.
-
No editorializing titles: You can add the author or website's name if helpful, but keep article titles unchanged.
-
No piracy or unverified APKs: Do not share links or direct people to pirated content or unverified APKs, which may contain malicious code.
-
No unauthorized polls, bots, or giveaways: Do not create polls, use bots, or organize giveaways without first contacting mods for approval.
-
No offensive or low-effort content: Don't post offensive or unhelpful content. Keep it civil and friendly!
-
No affiliate links: Posting affiliate links is not allowed.
Quick Links
Our Communities
- !askandroid@lemdro.id
- !androidmemes@lemdro.id
- !techkit@lemdro.id
- !google@lemdro.id
- !nothing@lemdro.id
- !googlepixel@lemdro.id
- !xiaomi@lemdro.id
- !sony@lemdro.id
- !samsung@lemdro.id
- !galaxywatch@lemdro.id
- !oneplus@lemdro.id
- !motorola@lemdro.id
- !meta@lemdro.id
- !apple@lemdro.id
- !microsoft@lemdro.id
- !chatgpt@lemdro.id
- !bing@lemdro.id
- !reddit@lemdro.id
Lemmy App List
Chat and More
view the rest of the comments
Neither microg or grapheneos solves all problems. I don't think the question here is mainly about google's tracking components, I think it is instead about system design to avoid leaking data.
That being said, as far as I know accelerometer and compass is still available to apps in an unrestricted manner even in the background, similarly with the speaker through which apps are still allowed to produce sounds that your can't hear, but tracking systems in the mall or even in smart devices at home listen to it.
The same can really be said about any other sensor with the exception of the mic and the cams because of permissions, but the impact of permissions really get nullified when your smartphone comes from the factory with 3 facebook apps installed, where 2 of them is an unremovable system app with all permissions granted. You still can't limit whether an app should have access to devices on the LAN when connected to WiFi, which means your phone (through a malicious app) can act as a gateway for tracking data if let's say you have blocked your smart tv from internet access (either directly, or by just the facebook app scraping all information of all devices on your network, that may also include data in how you use it (screen on time hours), or collected data that was expected accidentally or not).
There are several other points here too that I haven't mentioned.
MicroG & GrapheneOS projects specialize in blocking non-essential tracking related connections to Google. They are effective at that too.
Doesn't sound like an Android problem as any device with a speaker can be abused if I understand what you are saying.
Can't speak for compass & accelerometer permissions but how do you expect auto-rotation to work in apps?
Do you really expect people to push a consent toggle every time they visit pornhub.com. Be serious.
I think you are overthinking this. The concern here should be can Google or any other party exfiltrate this offline data and if so, what can you do to stop it?
Popping up a Wireshark equivalent and monitoring the chatter on your device is a good place to start. Otherwise you would be making cases for where there is no argument to be made.
Part of auto-rotation has always been happening in the system.
It's not the apps detecting when they need to rotate, but the system tells them about it.
Apps don't need access to precise sensor data.
I am really not. You may have said that 40 years ago and it would be fine, but nowadays it's not just scientists running professional software on their computers that's virtually granted to not do anything wrong, we all run apps that we don't completely trust, because it's not possible.
If that wouldn't be the case, we wouldn't have permission toggles for microphone and network access.
Oh, they can, and you will see it if you read my previous comment in whole.
If it doesn't happen today, that does not mean it won't ever.
Also, apps can detect if a VPN is active (which is required for capturing packets in a way that allows you to see the source app) and change their behavior. And then I doubt that you can capture broadcast messages that way, because why would that be routed through a VPN? (even when not a real one)
You have a lot of theory but unfortunately proof is needed for the paranoid claims you insist on making.
Am wary of the potential of developers abusing Android permissions in their apps and doing unwanted things on our devices. As a privacy enthusiast I try to limit the number of app installs to essential need only.
But Google Play store have a review process for vetting apps and Android in general has a strong sandbox for apps.
About tracking with smart devices and inaudible sounds: https://www.cityfreqs.com.au/pilfer.php
About tracking the accelerometer, gyroscope data: https://www.reddit.com/r/StallmanWasRight/comments/13u78hn/researchers_found_that_inconspicuous_smartphone/ (another discussion on the same source)
About cooperated tracking between your devices on your home network: I think you can see it yourself if you have worked with a computer network, as really it's just about untrusted computers being able to communicate.
They don't need to abuse permissions, because, as I said, a lot of things are unfortunately not gated by permissions.
You're gonna need better sources if you are going to convince anyone that phones are listening to you with mic permission disabled.
That said, I think you know what to do if you are getting your news from the RMS sub. None of these privacy violations, if they exist, would happen to you if you used a Linux phone.
By the way, it seems there are companies who claim to do this: https://lemm.ee/post/14867323
Honestly, I'm not shocked at all. Smart TVs don't usually gate microphone access behind a permission, and even on smartphones, it's very plausible to me that most people just allow any and all permission popup mindlessly.
Yes, I'm not one of those. But my environment is filled with people who don't care about tech and privacy at all, and with their behavior they compromise my privacy too.
I don't remember saying that. Can you point to where have I said that?
I have mentioned microphone tracking because even when put behind a permission, it is still a concern for apps for which you have allowed microphone access for some reason, often because you didn't really have a choice.
There are many other problems other than that, though, that I have mentioned but you didn't address.
Yeah probably, but this is an Android community, not a Linux one, and OP has had a question on the topic