Originally posted by starshipeleven
View Post
Announcement
Collapse
No announcement yet.
Android Q Reaches Public Beta With Improved Privacy, Opus/AV1 Support, ANGLE On Vulkan
Collapse
X
-
-
Originally posted by ldesnogu View PostOK so you can't guarantee privacy
As long as everyone you call is using that app to receive, anyway.
Is it how NSA spies calls?
That's why they are extremely butthurt about applications implementing end-to-end encryption over TCP/IP. Actually spying that is a whole another game.
Comment
-
Originally posted by Vistaus View PostI agree that root is a bit of a dirty hack, but sometimes it's needed for even basic functionality. For example, if you don't have a Samsung, you can't change the default font so you need root for that.
Comment
-
Originally posted by ldesnogu View PostVoice as starshipeleven wrote.
Comment
-
Originally posted by re:fi.64 View Post
Calendar and messages? Neither of those are even a disabled toggle on the settings.
Microphone makes sense for voice translation.
Also, check Google Pay out! https://i.imgur.com/ZHgdMgO.jpg
Comment
-
Originally posted by m132 View PostThat's because you're looking at the wrong package. Disable any of the permissions for Google Play Services (com.google.android.gms), restart your device and instead of the OCR you'll get a precious stack trace yelling about a "permission denial". Pretty clever technique to fool people into thinking that Google ain't abusing your phones, eh?
That's one of the reasons why Play Services asks so much permissions. It's also a "system library" of sorts used by other apps.
Although I don't understand why removing any permission causes breakage. I disabled all permissions on Play store and also Play services in my work phone (Huawei) and all apps I installed still work fine.Last edited by starshipeleven; 15 March 2019, 01:18 AM.
Comment
-
Originally posted by starshipeleven View PostIt just means that Samsung's shitty OCR application is actually just a GUI using Google Play Services OCR/Vision API to do the actual work.
Originally posted by starshipeleven View PostThat's one of the reasons why Play Services asks so much permissions. It's also a "system library" of sorts used by other apps.
Comment
-
Originally posted by m132 View PostExcept that the app we're talking about is Google Translate, made by Google themselves, and no Samsung is involved here I guess. Even if this API is being used there, I still fail to see how is body sensors access crucial to extract the text from a still image.
The popup screenshot I've linked to in my previous post displays the actual list of permissions the requestor wants. Some Google apps just show Storage, or Phone there, and this is completely understandable. Pay explicitly demands access to everything. What's your excuse now?
Telephone/SMS is usually used to identify the device through IMEI or SIM or something like that, other apps do it. Contacts is probably to send money to friends or whatever, which should not be a mandatory thing but I guess Google wants that to work?
But still, it's Google Pay. Even if it was not asking for that info it would still have payment information and your bank account or something. Anyone who remotely cares about privacy won't let Google know what they bought, when and from where anyway, so it's not terribly important.Last edited by starshipeleven; 15 March 2019, 03:45 AM.
Comment
-
Originally posted by starshipeleven View PostWeird, my Google Translate of realtime camera view works fine with all permissions disabled in Play Services. Can I shit-talk Samsung now? Because I really want to blame them for breaking this shit in their phone.
Originally posted by starshipeleven View PostTelephone/SMS is usually used to identify the device through IMEI or SIM or something like that, other apps do it. Contacts is probably to send money to friends or whatever, which should not be a mandatory thing but I guess Google wants that to work?
Originally posted by starshipeleven View Postother apps do itLast edited by m132; 15 March 2019, 04:23 AM.
Comment
-
Originally posted by m132 View PostInteresing, the AR translator seems to be working for me too. The problem comes up when you disable the instant mode or try to use the "pick from gallery" button.
The AR translator actually works offline as long as you have the offline dictionaries, and it's pretty decent as long as you are translating from "X language" to english.
Having access to any of these just to be able to send a few bytes over NFC is not required or even reasonable.
It is required (and should also be a good thing) to be able to identify and authorize the device for the very least, before it can be used to pay for things.
It also runs some tampering checks through SafetyNet https://koz.io/inside-safetynet/ (which aren't terribly hard to pass if you use something like Magisk for your root and advanced functionality, which is what you should be using on your device anyway if you are a power user)
You can read the statement if you try to add a credit card to Google Pay, it tells you that it may/will give that info to the credit card provider or something.
Just like having to explicitly allow Google to store your location and activity history in order to get a damn weather forecast on the homescreen.
Are you okay with this?
Comment
Comment