61–70 of 116 posts
Earlier quoted context omitted.
ROM is to android what distro is to Linux. The term is used correctly here. An android ROM could refer to the stock OS, GrapheneOS, LineageOS, Pixel Experience, etc.
With immutable distros (see bootc or systemd-sysupgrade) the operating system itself is also only just a read only file system. Does that count as ROM too?
Earlier quoted context omitted.
With immutable distros (see bootc or systemd-sysupgrade) the operating system itself is also only just a read only file system. Does that count as ROM too?
it's a term used for historical reasons, nobody is claiming it's accurately describing some technical property
Earlier quoted context omitted.
This isn't true. Roblox never had and does not have a kernel anti-cheat.
My mistake, I just assumed their Byfron anti-cheat is kernel level because that's the most common reason why anticheats take issue with Wine. If their anti-cheat operates entirely in usermode, then their decision to block Wine is even more baffling to me.
They encrypt every page and register an exception handler that decrypts the page when a fault is reached to keep memory secure. They do cache timing checks to see if a page was recently in the working set outside of the expected control flow and will flag you if you fail the check too many times because it indicates tampering.
Earlier quoted context omitted.
My understanding was that you have to install google messages to get RCS to work and on google's end it gets finicky about device ids. I read a couple blogs where people found RCS to be really unstable on GrapheneOS even with a couple workarounds. If I'm going to have to install a bunch of google products onto my phone anyways, I don't buy the benefits as much. I also had a recent experience being shaken down by a bo…
Basically all of Graphene's RCS issues have been fixed[0]. Additionally, your stance seems somewhat unusual - GrapheneOS isn't only meant to be used by people that have "something to hide". As for explaining it to border guard - it's just Android - if you're unlocking your phone for them anyway, they definitely shouldn't care about what flavor of Android you're running, whether it's LineageOS, ColorOS, GrapheneOS, et…
Makes sense for them to support this given their scale. I wouldn't be surprised if GrapheneOS secures another big Android OEM vendor (after Motorola Mobility) and the user base of the OS quickly grows from its current 400k+ to millions.
> after Motorola Mobility Does anyone know anymore on that front? For months, I've regularly looked up whether there were any news, only to find nothing besides the original announcement. No ETA, no upcoming devices to be supported, heck, on the Graphene side, their own webpages make nary a mention. Would buy a Razr 70 Ultra + Clicks the second that is confirmed, but for something that was so publicly announced month…
silently re-enables com.glance.lockscreenM one more time on you...
Remote attestation is still there and only official builds of GrapheneOS are supported. While this is marginally better than being tied to a build from an advertising company, you're still out of luck if you want to build the OS yourself.
Makes sense for them to support this given their scale. I wouldn't be surprised if GrapheneOS secures another big Android OEM vendor (after Motorola Mobility) and the user base of the OS quickly grows from its current 400k+ to millions.
If it become to big, it will go the same way as CyanogenMod, Google will send some people to pressure the manufacturers to drop them off
Earlier quoted context omitted.
If it become to big, it will go the same way as CyanogenMod, Google will send some people to pressure the manufacturers to drop them off
Google is the only one supporting them currently.
This is a really interesting signal tbh. While it sounds like it already works on GrapheneOS having a corporation come out and say they won't go out of their way to break it is quite unusual.
It requires a positive action from the application developer to include GrapheneOS's keys as well as Google's keys. So this is a deliberate positive step, rather than a default.
Earlier quoted context omitted.
This isn't true. Roblox never had and does not have a kernel anti-cheat.
My mistake, I just assumed their Byfron anti-cheat is kernel level because that's the most common reason why anticheats take issue with Wine. If their anti-cheat operates entirely in usermode, then their decision to block Wine is even more baffling to me.