Readit News logoReadit News
_vere commented on Motorola GrapheneOS devices will be bootloader unlockable/relockable   grapheneos.social/@Graphe... · Posted by u/pabs3
panny · 8 days ago
>but there really hasn't been any talk about how additional peripherals like aux would be a no-go.

It's water under the bridge. You're NEVER getting a Graphene phone that supports a microsd. It won't happen. The AUX jack, you will biligerently be told to get a USB DAC or otherwise you are an old man yelling at clouds.

Graphene and Motorola will work together by happy accident. Tell ya what though, if they make a GrapheneOS phone with 3.5mm, dual sim, microsd, and >no notch or hole punch< and I will buy it. I won't even care how much it costs. All the Xperias I've owned were among the most expensive phones on the market.

_vere · 8 days ago
It's unlikely for the Razr line to support microsd since those are foldables, and flagships like the signature line generally tend not to, but nowhere on their hardware requirements list does it say that a potentially supported device cannot have a microsd card slot, thats just wrong. There is nothing about a memory slot that would make the phone less safe inherently, they already support USB drives, internal emmc memory isnt that much more crazy than that, right? I just think its super weird to be like preemtively mad at them for an imagined aversion to supporting hardware that doesnt exist. I get that the people involved with the project can be a little prickly when you ask them for advice about stuff, but what do you expect them to do here? They support the devices they do not out of some sort of adherence to a skewed model of security, they actually genuinely need the hardware to be able to do all of the things they ask for, which currently literally only the pixel line offers. If a manufacturer like Sony who tends to do aux, microsd slots and no holepunch cameras were to adapt to their hardware standards (https://grapheneos.org/faq#future-devices) there would likely be an effort by people to get these supported, its not the lack of will from the devs, its the lack of support from phone manufacturers that has kept the line of supported devices constrained to pixels.
_vere commented on Motorola GrapheneOS devices will be bootloader unlockable/relockable   grapheneos.social/@Graphe... · Posted by u/pabs3
keerthiko · 9 days ago
Does anyone know where I can read more about which devices will be supported? GrapheneOS website devices FAQ doesn't list any Motorola devices, and the press release doesn't have much either.
_vere · 8 days ago
They said on Twitter that future devices in the Razr (foldable) and signature line will be supported. The current devices by Motorola do not fulfill their hardware requirements, so no need to buy one yet. This is speculation on my part, but its not unthinkable that non-flagship support could happen eventually, although mid tier SoCs generally don't have the hardware required to support graphene (hardware memory tagging, sufficiently open secure element, etc), so in the medium term, it's unlikely that anything but the flagships will be supported by graphene.
_vere commented on Motorola GrapheneOS devices will be bootloader unlockable/relockable   grapheneos.social/@Graphe... · Posted by u/pabs3
panny · 8 days ago
Lol, no, according to graphene, an aux jack is a security problem. So is a microsd. But the hole punch with the camera pointed at your face, that's just fine.

When my current phone dies, I'm basically returning to a dumb phone with a removable battery. Now that Xperia dropped open source, every phone out there is terrible and I just don't want any of them. Anything that would support a ROM has features to make my skin crawl.

_vere · 8 days ago
Their hardware requirements do not say this, where'd you get that idea? Graphene has stated they'll work with the Motorola team on supporting their devices, starting with the successors of the Razr foldable and the signature line, but there really hasn't been any talk about how additional peripherals like aux would be a no-go. USB is also a security concern, which is why they give you the option to disable it outright, disable data or disable until after-first-unlock. I don't see what would keep them from implementing this for aux, although since it's unidirectional I'm not sure if it even makes sense to compare aux to USB. They've supported pixels with aux ports in the past, and I don't think it's inclusion would be a blocking criteria. The comment about the camera is also kinda misguided. They zero out the camera input if you disable it, unlike traditional android. You can have a camera toggle in your quick settings and keep it disabled literally all the time. Enabling it when you bring up any camera related app takes either pin or biometrics, having the hardware here really shouldn't be a concern since you can look at how the code handling it works yourself. I'm not trying to convince you to use a pixel or a Motorola phone, do what you want, but at least be informed about stuff like this when you state things as if they are facts.
_vere commented on Colorado proposal moves age checks from websites to operating systems   biometricupdate.com/20260... · Posted by u/iamnothere
beej71 · 19 days ago
How is Linux going to do this?
_vere · 18 days ago
Treating Linux as a monolith here is kind of missing the point. Desktop Linux and Android have an entirely different application model, a solution for Android would have to be applied in a significantly different manner to desktop Linux. It'd likely be folded in to play services, as was the case with the exposure notification framework during covid for example.
_vere commented on Why we're taking legal action against SerpApi's unlawful scraping   blog.google/technology/sa... · Posted by u/xnx
_vere · 2 months ago
Move fast and break things unless they are the things owned by billionaires and gigacorps instead of stuff owned by normal people
_vere commented on Phone searches at the US border hit a record high   wired.com/story/phone-sea... · Posted by u/mikece
OutOfHere · 7 months ago
Does using GrapheneOS guard against such searches? Also, what is the future of GrapheneOS given that Google's release of the source code for Pixel's kernel was dropped, replaced with a generic image.
_vere · 7 months ago
To a degree. You have the duress pin, so you can wipe your phone quickly if need be. But I wouldn't call that guarding, your phone won't get searched but if TSA or ice saw you wipe your phone in front of them with a, to them, unknown feature, I doubt they'll let you enter the country.
_vere commented on Proton begins moving hardware out of Switzerland due to proposed legislation   techradar.com/vpn/vpn-pri... · Posted by u/terminalbraid
_vere · 7 months ago
Interesting they'd chose to move to germany with their infra after the whole "gov sued Tutanota into providing a backdoor into e2ee email and won" thing happened. I've been with proton specifically because they are one of the few privacy focused email providers that isnt based in germany. Maybe it's time to say screw it and host my own, even if deliverability is gonna be an issue. I don't feel like my email is safe if it's hosted in germany.
_vere commented on Graphene OS: a security-enhanced Android build   lwn.net/SubscriberLink/10... · Posted by u/madars
torium · 8 months ago
Does anybody else here see as problematic that this OS supports mostly Pixel, a Google phone?

Over and again people on HN make the following argument: "Google is a company that makes most of its revenue from ads and surveillance. Therefore, you should always assume that Google is spying on you". But somehow when it comes to Pixel people give it a pass?

Prediction: If Pixel isn't already hardwired to phone home and report on your activities, it will slowly become so over time, as Google realizes its interest. You know, as it happened with Android, Chrome, and everything else that Google touches.

_vere · 8 months ago
This is just conspiratorial fearmongering based on vibes. If pixels somehow phoned home on a hardware level, do you think we wouldn't be able to tell? Do you think we wouldn't see it in our network logs? GrapheneOS supports pixels because they are currently the only devices that fulfill their list of requirements, like an actually usable secure element, hardware memory tagging, etc. They have said and continue to reiterate that they would support other devices that fulfill their requirements and seem to be currently looking into working with OEMs to move away from pixels in the long term. Just saying "you claim to degoogle phones yet the phone you use is a GOOGLE pixel, suspicious" is baseless nonsense.
_vere commented on TapTrap: Animation‑Driven Tapjacking on Android   taptrap.click/... · Posted by u/Bogdanp
_vere · 8 months ago
Actually insane that this isn't patched in AOSP yet, literally the only android devices that aren't vulnerable are those running graphene. For companies as big as google, there really ought to be just disgusting financial penalties if they leave something like this unfixed for this amount of time.
_vere commented on I feel open source has turned into two worlds   utcc.utoronto.ca/~cks/spa... · Posted by u/sdht0
GardenLetter27 · 9 months ago
I don't mind them training on GPL code, but I wish they had to at least publish their model weights (and maybe also training and inference code, etc.) - same for the other issues re. using copyrighted media in training.
_vere · 9 months ago
Its not really about if you mind, they create derivative works in direct violation of the gpl.

u/_vere

KarmaCake day56June 14, 2023View Original